usage of Jenkins outside of github
Is there a way to pass jobs to Jenkins without opening a pullrequest? It seems that force-pushing too fast will confuse the scripts, they do not properly reset the tree if I interpret the logs correctly. As a result the PR enters failure state and can not be resumed without resetting the tree, push empty commits or do some other stunts to undo the changes within the PR.

Maybe one has to wait until all jobs are done until a force-push will work reliable?

GitHub pull request #15800 of commit e4ed38a3f9f37f5fd30a459d682c1a95a2d4247a, no merge conflicts.
Running as SYSTEM
Setting status of e4ed38a3f9f37f5fd30a459d682c1a95a2d4247a to PENDING with url and message: 'Found some time, building it now.'
[EnvInject] - Loading node environment variables.
[EnvInject] - Preparing an environment for the build.
[EnvInject] - Keeping Jenkins system variables.
[EnvInject] - Keeping Jenkins build variables.
[EnvInject] - Injecting contributions.
Building remotely on Linux-VM-2-Camelot (android linux buildall rbpi android-aarch64 android-arm64-v8a android-armv7 androidx86) in workspace /home/jenkins/workspace/BuildMulti-PR
Running Prebuild steps
Success build [email protected]
No credentials specified
> /usr/bin/git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
> /usr/bin/git config remote.origin.url git:// # timeout=10
Pruning obsolete local branches
Fetching upstream changes from git://
> /usr/bin/git --version # timeout=10
> /usr/bin/git fetch --tags --progress git:// +refs/pull/15800/merge:refs/remotes/origin/pr/15800/merge --prune
> /usr/bin/git rev-parse refs/remotes/origin/pr/15800/merge^{commit} # timeout=10
> /usr/bin/git rev-parse refs/remotes/origin/origin/pr/15800/merge^{commit} # timeout=10
Checking out Revision 57639f666b8b14d73faca3af1059cf14ca7c59d9 (refs/remotes/origin/pr/15800/merge)
> /usr/bin/git config core.sparsecheckout # timeout=10
> /usr/bin/git checkout -f 57639f666b8b14d73faca3af1059cf14ca7c59d9
Commit message: "Merge e4ed38a3f9f37f5fd30a459d682c1a95a2d4247a into 5033b6fd4e99f17fcb8b8f202958b8136c03b3bd"
> /usr/bin/git rev-list --no-walk 24fb0d9762093017daa4d4db269895176ce6eb56 # timeout=10
Set build name.
New build name is 'pr15800-1463cac'
[BuildMulti-PR] $ /bin/sh -xe /tmp/
ERROR: $GIT_COMMIT (1463cac2a2c0316bb4d98d3afc66cbd32ae4681d) doesn't match currently checked out revision (57639f666b8b14d73faca3af1059cf14ca7c59d9)
Build step 'Execute shell' marked build as failure
Set build name.
New build name is 'pr15800-1463cac'

There is a label "No Jenkins" you could attach to your PR. When you want to build a commit, simply remove it before force pushing.
Thread Rating:
  • 0 Vote(s) - 0 Average

Logout Mark Read Team Forum Stats Members Help
usage of Jenkins outside of github00