Hi Oliver,
On 18/03/18 12:19, Olivier Lamy wrote:
Hi
Just migrated to gitbox so considered as a new job/project here?
Yes I know but I observed that on other repos as well which are already
migrated..nevertheless need to continue to observe this...
Kind regards
Karl Heinz Marbaise
On Sun, 18 Mar 2018 at 21:03, Karl Heinz Marbaise <[email protected]> wrote:
Hi to all,
currently observing things like[1] this in console output:
Branch indexing
Obtained Jenkinsfile from 5e073791f9bb06cae1ed6513c8a5bde24844cf73
Running in Durability level: MAX_SURVIVABILITY
Loading library jenkins-env@master
Attempting to resolve master from remote references...
> git --version # timeout=10
> git ls-remote -h -t
https://gitbox.apache.org/repos/asf/maven-jenkins-env.git # timeout=10
Found match: refs/heads/master revision
7e5a8d991ba0cfb20727aa995304672a34b631bb
Cloning the remote Git repository
Cloning with configured refspecs honoured and without tags
Cloning repository
https://gitbox.apache.org/repos/asf/maven-jenkins-env.git
> git init
/x1/jenkins/jenkins-home/jobs/maven-box/jobs/maven-surefire/branches/master/workspace@libs
/jenkins-env
# timeout=10
Fetching upstream changes from
https://gitbox.apache.org/repos/asf/maven-jenkins-env.git
> git --version # timeout=
...
which gives me the impression that a build is triggered by a branch
indexing...
I would have expected that this should not trigger a build ?
Am I wrong?
@Stephen ?
Kind regards
Karl Heinz Marbaise
[1]:
https://builds.apache.org/view/M-R/view/Maven/job/maven-box/job/maven-surefire/job/master/1/consoleFull
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
