-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
Jenkins ver. 2.167
repo-plugin version 1.10.7
Actual behaviour:
- When repo-plugin is configured to poll manifest and an error occurs during repo sync, the plugin reports that changes are found
Expected behaviour:
- do not report any change, so the build is not launched
- notify that the polling is failing
Here's polling log:
... [poll] Latest remote head revision on refs/heads/release/jk/v1 is: 4792dd5dd91515eb13e2eabb828dc734e766bb33 - already built by 2 [src] $ /usr/bin/repo/repo init -u MY_GIT_SERVER_ADDRESS -b releaes/v1 -m mymanifest.xml fatal: could not read Username for 'MY_BITBUCKET_ADDRESS:port': No such device or address fatal: could not read Username for 'MY_BITBUCKET_ADDRESS:port': No such device or address fatal: cannot obtain manifest MY_MANIFEST_REPO_ADDRESS Done. Took 1 min 13 sec Changes found
Note: the bug report is for the "changes found", the connection issue is due to the fact that sometimes git credentials expires (since repo-plugin is not supporting Jenkins credentialsId like the git-plugin)
- relates to
-
JENKINS-37819 repo plugin spams build failures when manifest is unavailable.
- Open