[JIRA] (JENKINS-40374) stash Notifier not available on Jenkins Plugin-Manager
Title: Message Title Justen Britain commented on JENKINS-40374 Re: stash Notifier not available on Jenkins Plugin-Manager I just came here to report this as well. It has been missing since early November I believe. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-38419) Unable to detect PullRequest anymore
Title: Message Title Justen Britain commented on JENKINS-38419 Re: Unable to detect PullRequest anymore Related: https://issues.jenkins-ci.org/browse/JENKINS-40486 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-40486) Plugin does not adhere to documented global variables
Title: Message Title Justen Britain commented on JENKINS-40486 Re: Plugin does not adhere to documented global variables Related issue: https://issues.jenkins-ci.org/browse/JENKINS-38419 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-40486) Plugin does not adhere to documented global variables
Title: Message Title Justen Britain updated an issue Jenkins / JENKINS-40486 Plugin does not adhere to documented global variables Change By: Justen Britain The Jenkins local documentation for Pipelines declares that the following global variables will be populated:*CHANGE_ID * * CHANGE_URL * * CHANGE_TITLE * * CHANGE_AUTHOR * * CHANGE_AUTHOR_DISPLAY_NAME * * CHANGE_AUTHOR_EMAIL * * CHANGE_TARGET * The lack of data in these variables results in the following severely reduced functionality.* Unable to effectively notify users of pull request related build status via StashNotifier, HipChatNotifier, email and other notification plugins* Unable to effectively notify committers of build failures* Unable to detect pull requests without string parsing (which is hacky imo) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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
[JIRA] (JENKINS-40486) Plugin does not adhere to documented global variables
Title: Message Title Justen Britain created an issue Jenkins / JENKINS-40486 Plugin does not adhere to documented global variables Issue Type: Bug Assignee: Antonio Muñiz Components: bitbucket-branch-source-plugin Created: 2016/Dec/15 6:28 PM Environment: Jenkins 2.36 Bitbucket Server 4.11.1 Bitbucket plugin: Post Webhooks for Bitbucket bitbucket-branch-source-plugin 1.8 Labels: pipeline bitbucket notification global Priority: Major Reporter: Justen Britain The Jenkins local documentation for Pipelines declares that the following global variables will be populated: *CHANGE_ID CHANGE_URL CHANGE_TITLE CHANGE_AUTHOR CHANGE_AUTHOR_DISPLAY_NAME CHANGE_AUTHOR_EMAIL CHANGE_TARGET * The lack of data in these variables results in the following severely reduced functionality. Unable to effectively notify users of pull request related build status via StashNotifier, HipChatNotifier, email and other notification plugins Unable to effectively notify committers of build failures Unable to detect pull requests without string parsing (which is hacky imo)
[JIRA] (JENKINS-28877) Bitbucket Plugin unable to parse Bitbucket webhook response json
Title: Message Title Justen Britain commented on JENKINS-28877 Re: Bitbucket Plugin unable to parse Bitbucket webhook response json Frieder Rick I have cloned and built the develop branch of this project and tested with our Jenkins installation and the latest version of Bitbucket Server (formerly Stash), version 4.9.1. The problem that you and I are experiencing seems to be because Bitbucket Server is not explicitly supported in this way by this plugin (whether intentional or not). In fact, you will notice that in the code BitbucketHookReceiver.java there is a comment pointing to the Atlassian documentation for the webhooks. The URL provided results in a Page Not Found error with a suggestion to look at the documentation for Webhooks for Bitbucket Cloud (the latest branding for the hosted version of Bitbucket). It seems possible that at one time both "Stash" and the hosted Bitbucket may have been supported by the plugin. There are essentially three code paths available for the incoming payload, none of which are compatible with the payload that is being delivered by Bitbucket Server. That being said, the requirements to get this to work for Bitbucket Server would require the introduction of an additional code path to detect that the payload is being delivered from Bitbucket Server. The links below are from the "develop" branch and have been in pull request since April 30 with the latest comments on Aug 11. So it is unlikely that we will see a fix to this "bug" in the near future. I have attached the output from Bitbucket Server (modified to remove company information) and the links to the relevant code below: Note: Please notice these links point to the develop branch https://github.com/jenkinsci/bitbucket-plugin/blob/develop/src/main/java/com/cloudbees/jenkins/plugins/BitbucketHookReceiver.java#L81 https://github.com/jenkinsci/bitbucket-plugin/blob/develop/src/main/java/com/cloudbees/jenkins/plugins/payload/BitbucketPayload.java#L51 bb-server-4.9.1_payload.txt I was only able to dedicate a couple hours to investigating this issue so please forgive any oversights that may have been made. Add Comment
[JIRA] (JENKINS-28877) Bitbucket Plugin unable to parse Bitbucket webhook response json
Title: Message Title Justen Britain edited a comment on JENKINS-28877 Re: Bitbucket Plugin unable to parse Bitbucket webhook response json [~entfrickler] I have cloned and built the develop branch of this project and tested with our Jenkins installation and the latest version of Bitbucket Server (formerly Stash), version 4.9.1. The problem that you and I are experiencing seems to be because Bitbucket Server is not explicitly supported in this way by this plugin (whether intentional or not). In fact, you will notice that in the code [ BitbucketHookReceiver.java |https://github.com/jenkinsci/bitbucket-plugin/blob/develop/src/main/java/com/cloudbees/jenkins/plugins/BitbucketHookReceiver.java#L65] there is a comment pointing to the Atlassian documentation for the webhooks. The URL provided results in a Page Not Found error with a suggestion to look at the documentation for Webhooks for Bitbucket Cloud (the latest branding for the hosted version of Bitbucket). It seems possible that at one time both "Stash" and the hosted Bitbucket may have been supported by the plugin. There are essentially three code paths available for the incoming payload, none of which are compatible with the payload that is being delivered by Bitbucket Server. That being said, the requirements to get this to work for Bitbucket Server would require the introduction of an additional code path to detect that the payload is being delivered from Bitbucket Server. The links below are from the "develop" branch and have been in [pull request|https://github.com/jenkinsci/bitbucket-plugin/pull/30] since April 30 with the latest comments on Aug 11. So it is unlikely that we will see a fix to this "bug" in the near future.I have attached the output from Bitbucket Server (modified to remove company information) and the links to the relevant code below:_Note: Please notice these links point to the develop branch_* https://github.com/jenkinsci/bitbucket-plugin/blob/develop/src/main/java/com/cloudbees/jenkins/plugins/BitbucketHookReceiver.java#L81* https://github.com/jenkinsci/bitbucket-plugin/blob/develop/src/main/java/com/cloudbees/jenkins/plugins/payload/BitbucketPayload.java#L51[^bb-server-4.9.1_payload.txt]I was only able to dedicate a couple hours to investigating this issue so please forgive any oversights that may have been made. Add Comment
[JIRA] (JENKINS-28877) Bitbucket Plugin unable to parse Bitbucket webhook response json
Title: Message Title Justen Britain updated an issue Jenkins / JENKINS-28877 Bitbucket Plugin unable to parse Bitbucket webhook response json Change By: Justen Britain Attachment: bb-server-4.9.1_payload.txt Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-28877) Bitbucket Plugin unable to parse Bitbucket webhook response json
Title: Message Title Justen Britain updated an issue Jenkins / JENKINS-28877 Bitbucket Plugin unable to parse Bitbucket webhook response json Change By: Justen Britain Comment: I don't see a 1.5, do you mean 1.1.5? I can confirm the bug replicates in that version as well. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-28877) Bitbucket Plugin unable to parse Bitbucket webhook response json
Title: Message Title Justen Britain commented on JENKINS-28877 Re: Bitbucket Plugin unable to parse Bitbucket webhook response json I don't see a 1.5, do you mean 1.1.5? I can confirm the bug replicates in that version as well. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-28877) Bitbucket Plugin unable to parse Bitbucket webhook response json
Title: Message Title Justen Britain updated an issue Jenkins / JENKINS-28877 Bitbucket Plugin unable to parse Bitbucket webhook response json Change By: Justen Britain Environment: jenkins Jenkins 1.617, bitbucket-plugin 1.1.0 Jenkins 2.25, bitbucket-plugin 1.1.5 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-38211) JenkinsFiles cannot run on Linux agent of Windows master
Title: Message Title Justen Britain edited a comment on JENKINS-38211 Re: JenkinsFiles cannot run on Linux agent of Windows master Some additional information that I didn't feel was appropriate for the description as it is a bit speculative. Looking into the "bad interpreter: No such file or directory" output, it seems that most of the time this is related to windows style EOL characters in the script that is attempting to run. I verified that the JenkinsFile did not have the windows specific ^M line endings, to no avail. My hunch as to what is happening is that the command, "sh mvn test" is getting converted to a script, due to this line of output "sh: /opt/jenkins/workspace/ProjectName - TestMultiBranchPipeline/developer-branch-1@tmp/durable-6f9c6a38/script.sh:" and that script is either: 1. Getting created on the windows machine and copied to the node causing it to have windows style line endings2. Getting created by the windows master as a bash script and copied to on the node causing the windows line endings Again this is speculative but seemed worth adding to the comments. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-38211) JenkinsFiles cannot run on Linux agent of Windows master
Title: Message Title Justen Britain commented on JENKINS-38211 Re: JenkinsFiles cannot run on Linux agent of Windows master Some additional information that I didn't feel was appropriate for the description as it is a bit speculative. Looking into the "bad interpreter: No such file or directory" output, it seems that most of the time this is related to windows style EOL characters in the script that is attempting to run. I verified that the JenkinsFile did not have the windows specific ^M line endings, to no avail. My hunch as to what is happening is that the command, "sh mvn test" is getting converted to a script, due to this line of output "sh: /opt/jenkins/workspace/ProjectName - TestMultiBranchPipeline/developer-branch-1@tmp/durable-6f9c6a38/script.sh:" and that script is either: 1. Getting created on the windows machine and copied to the node causing it to have windows style line endings 2. Getting created by the windows master as a bash script and copied to the node Again this is speculative but seemed worth adding to the comments. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-38211) JenkinsFiles cannot run on Linux agent of Windows master
Title: Message Title
Justen Britain created an issue
Jenkins / JENKINS-38211
JenkinsFiles cannot run on Linux agent of Windows master
Issue Type:
Bug
Assignee:
Jesse Glick
Components:
pipeline
Created:
2016/Sep/14 6:36 PM
Environment:
Operating System: (master)Windows Server 2012 R2 64-bit, (slave/agent)amazon-linux-ami 2016.03-release 64-bit JRE/JDK: (master) 1.8.0_20, (slave/agent) 1.8.0_45 Jenkins Verison: 2.17 Plugin Versions: pipeline 2.2 pipeline-build-step 2.2 pipeline-input-step 2.1 pipeline-rest-api 1.7 pipeline-stage-step 2.1 pipeline-stage-view 1.7 Running as Jenkins service, not in Tomcat Reverse Proxy: No Jenkins Install Method: Windows Installer Slave Deploy method: via SSH Browser Version: Chrome - Version 53.0.2785.113 (64-bit)
Labels:
pipeline windows linux
Priority:
Major
Reporter:
Justen Britain
In a multi-branch pipeline using a JenkinsFile in the SCM it does not appear to be possible to execute 'sh' commands on a Linux node/agent. As per the example below, when using the 'sh' command in the JenkinsFile it causes a 'bad interpreter' error. JenkinsFile Snippit:
node('linux-agent-1') {
String jdktool = tool name: "1.7", type: 'hudson.model.JDK'
withEnv(["PATH+MVN=${tool 'Maven 2'}/bin", "PATH+JDK=${jdktool}/bin", "JAVA_HOME=${jdktool}"]) {
stage 'Checkout'
checkout scm
stage 'Build'
