-
Bug
-
Resolution: Incomplete
-
Major
-
None
Most of the time replay-pipeline works correctly, but in some rare cases it stops working for day or so, just out ot the blue.
java -jar ~/jenkins-cli.jar -s http://ltxl1168.sgdcelab.sabre.com:8080 replay-pipeline "Trip-Source-master" < Jenkinsfile ERROR: Not authorized to replay builds of this job
I'm using ssh keys for authorization, few minutes ago it was working, I disconnected from VPN and connected again and now I get the above error. This is second time it is happening.
Is there some cache on the jenkins side that remembers my IP address for authorization purposes?
Steps to reproduce:
1. Create Jenkinsfile with syntax error
2.
java -jar ~/jenkins-cli.jar -s http://ltxl1168.sgdcelab.sabre.com:8080 replay-pipeline "Trip-Source-master" < Jenkinsfile
3. Wait for the build to fail
4.
java -jar ~/jenkins-cli.jar -s http://ltxl1168.sgdcelab.sabre.com:8080 replay-pipeline "Trip-Source-master" < Jenkinsfile
Result of the last call:
ERROR: Not authorized to replay builds of this job
To make it work again, use replay job from the UI in Jenkins and paste a Jenkinsfile without syntax error, wait for the build to pass, now using CLI will work also.
- is related to
-
JENKINS-37589 Replay link does not show up if Jenkinsfile had a syntax error
-
- Open
-
[JENKINS-34555] replay-pipeline fails if previous replay resulted in Jenkinsfile syntax error
Description |
Original:
Most of the time replay-pipeline works correctly, but in some rare cases it stops working for day or so, just out ot the blue. {code} java -jar ~/jenkins-cli.jar -s http://ltxl1168.sgdcelab.sabre.com:8080 replay-pipeline "Trip-Source-master" < Jenkinsfile ERROR: Not authorized to replay builds of this job {code} I'm using ssh keys for authorization, few minutes ago it was working, I disconnected from VPN and connected again and now I get the above error. This is second time it is happening. Is there some cache on the jenkins side that remembers my IP address for authorization purposes? |
New:
Most of the time replay-pipeline works correctly, but in some rare cases it stops working for day or so, just out ot the blue. {code} java -jar ~/jenkins-cli.jar -s http://ltxl1168.sgdcelab.sabre.com:8080 replay-pipeline "Trip-Source-master" < Jenkinsfile ERROR: Not authorized to replay builds of this job {code} I'm using ssh keys for authorization, few minutes ago it was working, I disconnected from VPN and connected again and now I get the above error. This is second time it is happening. Is there some cache on the jenkins side that remembers my IP address for authorization purposes? Steps to reproduce: 1. Create Jenkinsfile with syntax error 2. java -jar ~/jenkins-cli.jar -s http://ltxl1168.sgdcelab.sabre.com:8080 replay-pipeline "Trip-Source-master" < Jenkinsfile 3. Wait for the build to fail 4. java -jar ~/jenkins-cli.jar -s http://ltxl1168.sgdcelab.sabre.com:8080 replay-pipeline "Trip-Source-master" < Jenkinsfile Result of the last call: {code} ERROR: Not authorized to replay builds of this job |
Description |
Original:
Most of the time replay-pipeline works correctly, but in some rare cases it stops working for day or so, just out ot the blue. {code} java -jar ~/jenkins-cli.jar -s http://ltxl1168.sgdcelab.sabre.com:8080 replay-pipeline "Trip-Source-master" < Jenkinsfile ERROR: Not authorized to replay builds of this job {code} I'm using ssh keys for authorization, few minutes ago it was working, I disconnected from VPN and connected again and now I get the above error. This is second time it is happening. Is there some cache on the jenkins side that remembers my IP address for authorization purposes? Steps to reproduce: 1. Create Jenkinsfile with syntax error 2. java -jar ~/jenkins-cli.jar -s http://ltxl1168.sgdcelab.sabre.com:8080 replay-pipeline "Trip-Source-master" < Jenkinsfile 3. Wait for the build to fail 4. java -jar ~/jenkins-cli.jar -s http://ltxl1168.sgdcelab.sabre.com:8080 replay-pipeline "Trip-Source-master" < Jenkinsfile Result of the last call: {code} ERROR: Not authorized to replay builds of this job |
New:
Most of the time replay-pipeline works correctly, but in some rare cases it stops working for day or so, just out ot the blue. {code} java -jar ~/jenkins-cli.jar -s http://ltxl1168.sgdcelab.sabre.com:8080 replay-pipeline "Trip-Source-master" < Jenkinsfile ERROR: Not authorized to replay builds of this job {code} I'm using ssh keys for authorization, few minutes ago it was working, I disconnected from VPN and connected again and now I get the above error. This is second time it is happening. Is there some cache on the jenkins side that remembers my IP address for authorization purposes? Steps to reproduce: 1. Create Jenkinsfile with syntax error 2. {code}java -jar ~/jenkins-cli.jar -s http://ltxl1168.sgdcelab.sabre.com:8080 replay-pipeline "Trip-Source-master" < Jenkinsfile{code} 3. Wait for the build to fail 4. {code}java -jar ~/jenkins-cli.jar -s http://ltxl1168.sgdcelab.sabre.com:8080 replay-pipeline "Trip-Source-master" < Jenkinsfile{code} Result of the last call: {code} ERROR: Not authorized to replay builds of this job {code} |
Description |
Original:
Most of the time replay-pipeline works correctly, but in some rare cases it stops working for day or so, just out ot the blue. {code} java -jar ~/jenkins-cli.jar -s http://ltxl1168.sgdcelab.sabre.com:8080 replay-pipeline "Trip-Source-master" < Jenkinsfile ERROR: Not authorized to replay builds of this job {code} I'm using ssh keys for authorization, few minutes ago it was working, I disconnected from VPN and connected again and now I get the above error. This is second time it is happening. Is there some cache on the jenkins side that remembers my IP address for authorization purposes? Steps to reproduce: 1. Create Jenkinsfile with syntax error 2. {code}java -jar ~/jenkins-cli.jar -s http://ltxl1168.sgdcelab.sabre.com:8080 replay-pipeline "Trip-Source-master" < Jenkinsfile{code} 3. Wait for the build to fail 4. {code}java -jar ~/jenkins-cli.jar -s http://ltxl1168.sgdcelab.sabre.com:8080 replay-pipeline "Trip-Source-master" < Jenkinsfile{code} Result of the last call: {code} ERROR: Not authorized to replay builds of this job {code} |
New:
Most of the time replay-pipeline works correctly, but in some rare cases it stops working for day or so, just out ot the blue. {code} java -jar ~/jenkins-cli.jar -s http://ltxl1168.sgdcelab.sabre.com:8080 replay-pipeline "Trip-Source-master" < Jenkinsfile ERROR: Not authorized to replay builds of this job {code} I'm using ssh keys for authorization, few minutes ago it was working, I disconnected from VPN and connected again and now I get the above error. This is second time it is happening. Is there some cache on the jenkins side that remembers my IP address for authorization purposes? Steps to reproduce: 1. Create Jenkinsfile with syntax error 2. {code}java -jar ~/jenkins-cli.jar -s http://ltxl1168.sgdcelab.sabre.com:8080 replay-pipeline "Trip-Source-master" < Jenkinsfile{code} 3. Wait for the build to fail 4. {code}java -jar ~/jenkins-cli.jar -s http://ltxl1168.sgdcelab.sabre.com:8080 replay-pipeline "Trip-Source-master" < Jenkinsfile{code} Result of the last call: {code} ERROR: Not authorized to replay builds of this job {code} To make it work again, use replay job from the UI in Jenkins and paste a Jenkinsfile without syntax error, wait for the build to pass, now using CLI will work also. |
Description |
Original:
Most of the time replay-pipeline works correctly, but in some rare cases it stops working for day or so, just out ot the blue. {code} java -jar ~/jenkins-cli.jar -s http://ltxl1168.sgdcelab.sabre.com:8080 replay-pipeline "Trip-Source-master" < Jenkinsfile ERROR: Not authorized to replay builds of this job {code} I'm using ssh keys for authorization, few minutes ago it was working, I disconnected from VPN and connected again and now I get the above error. This is second time it is happening. Is there some cache on the jenkins side that remembers my IP address for authorization purposes? Steps to reproduce: 1. Create Jenkinsfile with syntax error 2. {code}java -jar ~/jenkins-cli.jar -s http://ltxl1168.sgdcelab.sabre.com:8080 replay-pipeline "Trip-Source-master" < Jenkinsfile{code} 3. Wait for the build to fail 4. {code}java -jar ~/jenkins-cli.jar -s http://ltxl1168.sgdcelab.sabre.com:8080 replay-pipeline "Trip-Source-master" < Jenkinsfile{code} Result of the last call: {code} ERROR: Not authorized to replay builds of this job {code} To make it work again, use replay job from the UI in Jenkins and paste a Jenkinsfile without syntax error, wait for the build to pass, now using CLI will work also. |
New:
Most of the time replay-pipeline works correctly, but in some rare cases it stops working for day or so, just out ot the blue. {code} java -jar ~/jenkins-cli.jar -s http://ltxl1168.sgdcelab.sabre.com:8080 replay-pipeline "Trip-Source-master" < Jenkinsfile ERROR: Not authorized to replay builds of this job {code} I'm using ssh keys for authorization, few minutes ago it was working, I disconnected from VPN and connected again and now I get the above error. This is second time it is happening. Is there some cache on the jenkins side that remembers my IP address for authorization purposes? *Steps to reproduce:* 1. Create Jenkinsfile with syntax error 2. {code}java -jar ~/jenkins-cli.jar -s http://ltxl1168.sgdcelab.sabre.com:8080 replay-pipeline "Trip-Source-master" < Jenkinsfile{code} 3. Wait for the build to fail 4. {code}java -jar ~/jenkins-cli.jar -s http://ltxl1168.sgdcelab.sabre.com:8080 replay-pipeline "Trip-Source-master" < Jenkinsfile{code} Result of the last call: {code} ERROR: Not authorized to replay builds of this job {code} To make it work again, use replay job from the UI in Jenkins and paste a Jenkinsfile without syntax error, wait for the build to pass, now using CLI will work also. |
Summary | Original: replay-pipeline randomly fails to authorize | New: replay-pipeline fails if previous replay resulted in failed build |
Summary | Original: replay-pipeline fails if previous replay resulted in failed build | New: replay-pipeline fails if previous replay resulted in Jenkinsfile syntax error |
Component/s | Original: cli [ 15624 ] |
Resolution | New: Incomplete [ 4 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Workflow | Original: JNJira [ 170701 ] | New: JNJira + In-Review [ 198927 ] |
Component/s | New: pipeline-general [ 21692 ] |