1

The component used to be checked out by Jenkins as a whole dir. Don't know why it starts to check it out as separate subdirs.

For example:

it should've checked out the componnet as:

/com (it has sub dirs like /src, /include, etc)

instead, it checks it out as:

/src
/include
/doc
...

And this only happens to this component, not seen on other components.

EDIT:

  1. The log screenshot: (as you can see, the /include, /doc are checked out seperately) enter image description here

  2. The configuration of Jenkins: enter image description here

Henry
  • 2,819
  • 3
  • 18
  • 33
  • Could you provide more information how you configured the checkout? It sounds like a configuration issue. Maybe you configured it in a way that tells Jenkins that you want to have the content of a directory and not the parent directory itself. Like that: 'repo/com/' -> content without parent, 'repo/com' -> parent and its content. – Thomas Herzog May 01 '19 at 09:55
  • @ThomasHerzog I don't think that's the cause. We have no control to that kind of detail, all we did was just pick this component in a dialog window and hit "OK" button. – Henry May 02 '19 at 00:03
  • could you provide the config of jenkins, where you define the checkout? Is it SVN or GIT? – Thomas Herzog May 02 '19 at 05:05
  • @ThomasHerzog We define the checkout in "Build definition" in RTC, more specifically, in the workspace of "build Definition". We use SCM as version control for RTC – Henry May 02 '19 at 13:29
  • I mean, shouldn't Jenkins's problem, right? why do other components get checked out properly? – Henry May 02 '19 at 13:30
  • I am not really familiar with RTC on Jenkins, but is there something different with this problematic component compared to the other components? When you look at the workspace are only the subdirs checked out, or is the execution just done within the component and your are mislead? When the other components work, then it sounds like the problematic component differs from the others somehow. – Thomas Herzog May 02 '19 at 17:32
  • That's where I feel confused, too. Only the subdirs got checked out and this component is the same with others, no specific config for it. – Henry May 02 '19 at 18:06
  • Could you provide logs and the job configuration? – Thomas Herzog May 02 '19 at 18:31
  • How do I share it? – Henry May 02 '19 at 19:45
  • Add it as images for instance – Thomas Herzog May 03 '19 at 07:12
  • @ThomasHerzog Added – Henry May 03 '19 at 15:25
  • The logs and config does not tell much. Did you try to create a new job to check if occurrs there as well? Don't know how to help any further – Thomas Herzog May 03 '19 at 17:02
  • That might be a good idea. Let me try – Henry May 03 '19 at 19:07
  • @ThomasHerzog The config and logs seem very normal. And just let you know that I tried creating a new jenkins job and it doesn't work, same issue. – Henry May 03 '19 at 19:53
  • I am afraid I cannot help you any further. Report an issue at https://issues.jenkins-ci.org/projects/JENKINS/issues/JENKINS-54126?filter=allopenissues maybe those guys can help you, if no one else at stackoverflow can help you – Thomas Herzog May 05 '19 at 08:14

0 Answers0