[JIRA] (JENKINS-53821) credentials invalid only in githubNotify
Title: Message Title Victor Bjelkholm commented on JENKINS-53821 Re: credentials invalid only in githubNotify We're having the same issue as well with no solution in sight. It seemingly started breaking without us making any changes. This is the full error we're getting: Also: java.lang.IllegalArgumentException: The supplied credentials are invalid to login java.lang.IllegalArgumentException: The supplied credentials are invalid to login at org.jenkinsci.plugins.pipeline.githubstatusnotification.GitHubStatusNotificationStep.getGitHubIfValid(GitHubStatusNotificationStep.java:263) at org.jenkinsci.plugins.pipeline.githubstatusnotification.GitHubStatusNotificationStep.getRepoIfValid(GitHubStatusNotificationStep.java:268) at org.jenkinsci.plugins.pipeline.githubstatusnotification.GitHubStatusNotificationStep.access$100(GitHubStatusNotificationStep.java:79) at org.jenkinsci.plugins.pipeline.githubstatusnotification.GitHubStatusNotificationStep$Execution.run(GitHubStatusNotificationStep.java:373) at org.jenkinsci.plugins.pipeline.githubstatusnotification.GitHubStatusNotificationStep$Execution.run(GitHubStatusNotificationStep.java:355) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:47) at hudson.security.ACL.impersonate(ACL.java:290) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1.run(AbstractSynchronousNonBlockingStepExecution.java:44) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) Finished: FAILURE Add Comment This
[JIRA] (JENKINS-53766) Blue Ocean doesn't properly redirect when retrying stage in Firefox
Title: Message Title Victor Bjelkholm created an issue Jenkins / JENKINS-53766 Blue Ocean doesn't properly redirect when retrying stage in Firefox Issue Type: New Feature Assignee: Andrew Bayer Components: pipeline-model-definition-plugin Created: 2018-09-25 13:24 Priority: Minor Reporter: Victor Bjelkholm Currently the experience of retrying a stage when using Firefox is severely lacking. Instead of redirecting to the new job so the user has some feedback that it worked, it does nothing and stays on the same page. Behavior in Chrome works fine, but not Firefox. Add Comment
[JIRA] (JENKINS-53766) Blue Ocean doesn't properly redirect when retrying stage in Firefox
Title: Message Title Victor Bjelkholm updated an issue Jenkins / JENKINS-53766 Blue Ocean doesn't properly redirect when retrying stage in Firefox Change By: Victor Bjelkholm Issue Type: New Feature Bug Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53730) Automatically reuse stashes in declerative pipelines
Title: Message Title Victor Bjelkholm created an issue Jenkins / JENKINS-53730 Automatically reuse stashes in declerative pipelines Issue Type: New Feature Assignee: Andrew Bayer Components: pipeline-model-definition-plugin Created: 2018-09-22 09:45 Priority: Minor Reporter: Victor Bjelkholm With https://issues.jenkins-ci.org/browse/JENKINS-45455 in place and that it can retry pipelines from particular stages is great and saves a lot of time. What would be even greater would be the possibility to configure a declarative pipeline to automatically reuse previous stashes if some file has/hasn't changed. The way I imagine the feature to work is that you can give data for a `stash` call that it will use to either reuse a stash from the last successful run or compute it again. Not exactly sure how the syntax for this would look, but would need some way of declaring in the beginning of a stage what variable to look at before reusing a stash, and if needed, jumps ahead to a `unstash` call instead of stashing again. Add Comment
[JIRA] (JENKINS-47163) Use same workspace or node in multiple stages in pipeline
Title: Message Title Victor Bjelkholm assigned an issue to Victor Bjelkholm Jenkins / JENKINS-47163 Use same workspace or node in multiple stages in pipeline Change By: Victor Bjelkholm Assignee: Andrew Bayer Victor Bjelkholm Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
