[JIRA] (JENKINS-57182) When configuring a Jira steps site in casc yaml file. If the Jenkins service is restarted, the site is duplicated in Jenkins config
Title: Message Title
simon Wall created an issue
Jenkins / JENKINS-57182
When configuring a Jira steps site in casc yaml file. If the Jenkins service is restarted, the site is duplicated in Jenkins config
Issue Type:
Bug
Assignee:
Naresh Rayapati
Components:
jira-steps-plugin
Created:
2019-04-25 12:54
Labels:
jcasc-compatibility
Priority:
Minor
Reporter:
simon Wall
When configuring a Jira steps site, for example: unclassified: config: sites: name: JIRA url: "[url of site]" loginType: basic userName: [username] password: ${userpass-variable} timeout: 1 readTimeout: 1 If the Jenkins service is restarted, the site is duplicated.
Add Comment
[JIRA] (JENKINS-19058) ec2-plugin cannot add specified instance tags on launched spot instances
Title: Message Title simon Wall commented on JENKINS-19058 Re: ec2-plugin cannot add specified instance tags on launched spot instances Is there any further development on this ticket? I am hopeful to be able to make use of the EC2 plugin's ability to manage worker nodes using spot instances, but we need to have tags passed to the instance. 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-51021) plugin reporting error "java.lang.IllegalArgumentException: The supplied credentials are invalid to login" on latest version
Title: Message Title simon Wall commented on JENKINS-51021 Re: plugin reporting error "java.lang.IllegalArgumentException: The supplied credentials are invalid to login" on latest version I'm not sure if this is due to standard GutHub behaviour. As David Loomer has highlighted, the behaviour in the plugin has changed between versions. Using the odler verion, I can authenticate with the same gitHub Enterprise server using username and password, but with version 1.0.4 I only have success with an access token. It may be that there is also a relation to the version of GitHub enterprise that is running on the GH end, but there is definitely changes made in this plugin that causes the user's password to no longer be accepted. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-51021) plugin reporting error "java.lang.IllegalArgumentException: The supplied credentials are invalid to login" on latest version
Title: Message Title simon Wall edited a comment on JENKINS-51021 Re: plugin reporting error "java.lang.IllegalArgumentException: The supplied credentials are invalid to login" on latest version I'm not sure if this is due to standard GutHub behaviour. As [~dloomer] has highlighted, the behaviour in the plugin has changed between versions. Using the odler verion older version , I can authenticate with the same gitHub Enterprise server using username and password, but with version 1.0.4 I only have success with an access token.It may be that there is also a relation to the version of GitHub enterprise that is running on the GH end, but there is definitely changes made in this plugin that causes the user's password to no longer be accepted. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-51021) plugin reporting error "java.lang.IllegalArgumentException: The supplied credentials are invalid to login" on latest version
Title: Message Title simon Wall commented on JENKINS-51021 Re: plugin reporting error "java.lang.IllegalArgumentException: The supplied credentials are invalid to login" on latest version Thanks David Loomer, changing the password to a personal access token has resolved the issue. Raul Arabaolaza, could the documentation for this plugin please be updated to state that the password in the Username andPassword credentialsId should be a personal access token rather than the user's actual password? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-51021) plugin reporting error "java.lang.IllegalArgumentException: The supplied credentials are invalid to login" on latest version
Title: Message Title
simon Wall created an issue
Jenkins / JENKINS-51021
plugin reporting error "java.lang.IllegalArgumentException: The supplied credentials are invalid to login" on latest version
Issue Type:
Bug
Assignee:
Raul Arabaolaza
Components:
pipeline-githubnotify-step-plugin
Created:
2018-04-26 14:03
Priority:
Major
Reporter:
simon Wall
Using the following pipeline code:
githubNotify context: "Ansible-${ansVersion}",
credentialsId: 'generic-credentials-id',
description: 'Testing',
gitApiUrl: 'https://git.illumina.com/api/v3/',
status: 'PENDING'
works fine with version 1.0.1 of the plugin. However, using the latest version, (1.0.4) fails to build the pipeline, with exactly the same code and then reports the following when attempting to notify back to github again
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
[JIRA] (JENKINS-43266) credentialsId doesn't appear to work with github enterprise
Title: Message Title simon Wall created an issue Jenkins / JENKINS-43266 credentialsId doesn't appear to work with github enterprise Issue Type: Bug Assignee: Raul Arabaolaza Components: pipeline-githubnotify-step-plugin Created: 2017/Mar/31 11:37 AM Priority: Minor Reporter: simon Wall I have been trying out the Pipeline Githubnotify Step Plugin as part of notifying pull requests to a repo in a GitHub Enterprise environment. If I do not specify the credentialsId then the plugin reports back to GitHub Enterprise fine. But the following is reported at the end of the pipeline job processing: java.lang.IllegalArgumentException: The suplied credentials are invalid to login at org.jenkinsci.plugins.pipeline.githubstatusnotification.GitHubStatusNotificationStep.getGitHubIfValid(GitHubStatusNotificationStep.java:234) at org.jenkinsci.plugins.pipeline.githubstatusnotification.GitHubStatusNotificationStep.getRepoIfValid(GitHubStatusNotificationStep.java:239) at org.jenkinsci.plugins.pipeline.githubstatusnotification.GitHubStatusNotificationStep.access$100(GitHubStatusNotificationStep.java:75) at org.jenkinsci.plugins.pipeline.githubstatusnotification.GitHubStatusNotificationStep$Execution.run(GitHubStatusNotificationStep.java:344) at org.jenkinsci.plugins.pipeline.githubstatusnotification.GitHubStatusNotificationStep$Execution.run(GitHubStatusNotificationStep.java:326) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:47) at hudson.security.ACL.impersonate(ACL.java:213) 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:1142) at
