[JIRA] (JENKINS-40683) Create functional tests for some provided tokens
Title: Message Title Evaristo Gutierrez updated JENKINS-40683 Jenkins / JENKINS-40683 Create functional tests for some provided tokens Change By: Evaristo Gutierrez Status: In Review Resolved Resolution: Fixed 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-38221) Non informative error message when Marathon responds with HTTP 422
Title: Message Title Prabhuanand Sivashanmugam commented on JENKINS-38221 Re: Non informative error message when Marathon responds with HTTP 422 Will be nice, if you can capture the error message and display as an exception just before the stack trace. 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-40484) Unable to use withMaven step inside docker container
Title: Message Title dan tran updated an issue Jenkins / JENKINS-40484 Unable to use withMaven step inside docker container Change By: dan tran Priority: Critical Major 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-40484) Unable to use withMaven step inside docker container
Title: Message Title dan tran updated an issue Jenkins / JENKINS-40484 Unable to use withMaven step inside docker container Change By: dan tran Priority: Minor Critical 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-35432) Scheduled builds crash after running for more than 8 hours
Title: Message Title Supreet Singh commented on JENKINS-35432 Re: Scheduled builds crash after running for more than 8 hours I am also facing similar issue with Jenkins ver. 1.642.18.3 (CloudBees Jenkins Enterprise 15.11) and TFS plugin 5.2.1. After every 3-4 days all jobs start failing on windows slave and need a restart of slave service to fix the issue. Does anyone has a permanent fix for this issue? 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-40701) Add warning that Usage Tracking might not be exhaustive and depends on the consumer plugins
Title: Message Title Denys Digtiar created an issue Jenkins / JENKINS-40701 Add warning that Usage Tracking might not be exhaustive and depends on the consumer plugins Issue Type: Bug Assignee: Stephen Connolly Components: credentials-plugin Created: 2016/Dec/28 4:41 AM Priority: Minor Reporter: Denys Digtiar Until all the Credential consumers support the Usage Tracking API this feature might give a false impression that Credential is not used and can be deleted while it is still in use by the plugin which simply does not report the usage. Generic disclaimer or a way to detect and report the plugins which are not reporting usage should failproof this feature a bit. Add Comment
[JIRA] (JENKINS-40616) publishHTML on blueocean
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-40616 publishHTML on blueocean Change By: James Dumay Component/s: htmlpublisher-plugin 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-40614) L10N: Switch language of UI.
Title: Message Title James Dumay commented on JENKINS-40614 Re: L10N: Switch language of UI. Michael Hüttermann what happens if you load blue ocean with your cache disabled? Do you still see the german translation? 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-40616) publishHTML on blueocean
Title: Message Title James Dumay commented on JENKINS-40616 Re: publishHTML on blueocean Lewis Cowles I am assuming that this is provided by the HTML publisher plugin? 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-40619) Visualizing (list of sequential steps) as groups, as part of one stage
Title: Message Title James Dumay commented on JENKINS-40619 Re: Visualizing (list of sequential steps) as groups, as part of one stage Michael Hüttermann I think this is related to JENKINS-38442 but could you please provide an example Jenkinsfile pipeline script and screenshot of how it is currently rendered? 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-40619) Visualizing (list of sequential steps) as groups, as part of one stage
Title: Message Title
James Dumay edited a comment on JENKINS-40619
Re: Visualizing (list of sequential steps) as groups, as part of one stage
[~michaelhuettermann] I think this is related to JENKINS-38442 but could you please provide an example {{Jenkinsfile}} pipeline script and screenshot of how it is currently rendered to help clarify your request ?
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-40680) No/useless tooltips for time information on running build
Title: Message Title James Dumay resolved as Duplicate Duplicated by JENKINS-35849. Jenkins / JENKINS-40680 No/useless tooltips for time information on running build Change By: James Dumay Status: Open Resolved Resolution: Duplicate 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-40699) Declarative pipeline beta docs: how to collect test results from different nodes
Title: Message Title Kevin Burnett updated an issue Jenkins / JENKINS-40699 Declarative pipeline beta docs: how to collect test results from different nodes Change By: Kevin Burnett Summary: Declarative pipeline beta docs: how to collect test results from different nodes 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-39788) API to get all the repositories in an organization
Title: Message Title Vivek Pandey closed an issue as Fixed Closing, its being implemented as part of https://issues.jenkins-ci.org/browse/JENKINS-39789 See PR https://github.com/jenkinsci/blueocean-plugin/pull/673. Jenkins / JENKINS-39788 API to get all the repositories in an organization Change By: Vivek Pandey Status: In Progress Closed Resolution: Fixed 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
[JIRA] (JENKINS-40608) Job Summary Of Changes disappeared in version 1.4.12
Title: Message Title Ben Langton commented on JENKINS-40608 Re: Job Summary Of Changes disappeared in version 1.4.12 I cannot upgrade the plugin until this is resolved. 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-40693) badMessage: 400 Bad Host header for HttpChannelOverHttp
Title: Message Title Arnaud Héritier updated an issue Jenkins / JENKINS-40693 badMessage: 400 Bad Host header for HttpChannelOverHttp Change By: Arnaud Héritier Priority: Major Minor 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-40693) badMessage: 400 Bad Host header for HttpChannelOverHttp
Title: Message Title Arnaud Héritier commented on JENKINS-40693 Re: badMessage: 400 Bad Host header for HttpChannelOverHttp I had a doubt but we have nothing between Minor and Major The workaround is easy to apply but you need to find this issue (I hope it is correctly described/indexed to be found when required) and it a regression when you upgrade from 1.x to 2.x 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-40700) Display communication protocol in agent logs
Title: Message Title Sam Gleske commented on JENKINS-40700 Re: Display communication protocol in agent logs I opened https://github.com/jenkinsci/jenkins/pull/2682 to enhance the descriptions from the protocol getDisplayName(). 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-40693) badMessage: 400 Bad Host header for HttpChannelOverHttp
Title: Message Title Daniel Beck commented on JENKINS-40693 Re: badMessage: 400 Bad Host header for HttpChannelOverHttp Why is this "Major" when the workaround is obviously to set the Host header? What am I missing here? 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-40524) Rework agent syntax to be more extensible
Title: Message Title Andrew Bayer commented on JENKINS-40524 Re: Rework agent syntax to be more extensible Yes, validation will catch those cases. 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-40700) Display communication protocol in agent logs
Title: Message Title
Sam Gleske updated an issue
Jenkins / JENKINS-40700
Display communication protocol in agent logs
Change By:
Sam Gleske
It would be nice of if the Jenkins startup log for permanent slaves would output what protocols it was using to communicate with the master.h1. Current behaviorRight now the startup log looks something like:{code:none}JNLP agent connected from localhost/127.0.0.1Slave.jar version: 3.3This is a Unix agentNOTE: Relative remote path resolved to: /home/sam/sandbox/jenkinsAgent successfully connected and online{code}h1. Desired outputUnderneath {{Slave.jar version}} would be a good place to output the communication protocol. Something along the lines of:{code:none}JNLP agent connected from localhost/127.0.0.1Slave.jar version: 3.3Communication Protocol: Java Web Start Agent Protocol/4This is a Unix agentNOTE: Relative remote path resolved to: /home/sam/sandbox/jenkinsAgent successfully connected and online{code}Using the protocol {{getDisplayName()}} method.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-36871) JNLPProtocol4
Title: Message Title Sam Gleske commented on JENKINS-36871 Re: JNLPProtocol4 It would be nice if the agent Log output displayed which protocol it is using in the agent startup information. I created JENKINS-40700 as an enhancement. 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-40700) Display communication protocol in agent logs
Title: Message Title Sam Gleske created an issue Jenkins / JENKINS-40700 Display communication protocol in agent logs Issue Type: Improvement Assignee: Unassigned Components: remoting Created: 2016/Dec/27 10:51 PM Environment: Jenkins ver. 2.38 Priority: Minor Reporter: Sam Gleske It would be nice of the Jenkins startup log for permanent slaves would output what protocols it was using to communicate with the master. Current behavior Right now the startup log looks something like: JNLP agent connected from localhost/127.0.0.1 Slave.jar version: 3.3 This is a Unix agent NOTE: Relative remote path resolved to: /home/sam/sandbox/jenkins Agent successfully connected and online Desired output Underneath Slave.jar version would be a good place to output the communication protocol. Something along the lines of: JNLP agent connected from localhost/127.0.0.1 Slave.jar version: 3.3 Communication Protocol: Java Web Start Agent Protocol/4 This is a Unix agent NOTE: Relative remote path resolved to: /home/sam/sandbox/jenkins Agent successfully connected and online Using the protocol getDisplayName() method.
[JIRA] (JENKINS-40524) Rework agent syntax to be more extensible
Title: Message Title Michael Neale commented on JENKINS-40524 Re: Rework agent syntax to be more extensible I think the final "flattened" form suggested above looks quite good. The common cases will be quite clear, and it appears to be extensible. You often use label alongside docker so this makes sense to me as a user. Will validation catch things like a user putting in dockerArgs but not docker? if they put both docker and dockerFile etc? (can be a future enhancement, if not) 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-36871) JNLPProtocol4
Title: Message Title Sam Gleske commented on JENKINS-36871 Re: JNLPProtocol4 Nevermind, I found it in Manage Jenkins > Configure Global Security > JNLP. In the Advanced section, you have to enable JNLP4 (and can optionally disable the other protocols). Then if you look at the agent log you can see the JNLP4 class being used in the thread dump output. It would be nice if the agent Log output displayed which protocol it is using in the agent startup information. 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-40699) Declarative pipeline beta docs: how collect test results from different nodes
Title: Message Title
Kevin Burnett created an issue
Jenkins / JENKINS-40699
Declarative pipeline beta docs: how collect test results from different nodes
Issue Type:
Improvement
Assignee:
Andrew Bayer
Components:
pipeline-model-definition-plugin
Created:
2016/Dec/27 10:28 PM
Priority:
Minor
Reporter:
Kevin Burnett
If I want to run five different test suites, each having their own test result patterns, on five different nodes, in parallel, how do I do that? The abbreviated pipeline below all seems to work except for the collecting test results part, since when tests fail, the junit instruction is ignored (I guess since the previous step had a non-zero exit code). When not using the new declarative pipeline format, I could potentially use try/catch/finally and shove the junit instruction in the finally block as seen here. Current attempt:
pipeline {
agent label:'master'
environment {
GIT_COMMITTER_NAME = "jenkins"
GIT_COMMITTER_EMAIL = "jenk...@jenkins.io"
}
stages {
stage("Build") {
steps {
parallel (
"sweet" : {
node("has-docker") {
git 'ssh://g...@stash.example.com/automation/sweet.git'
sh 'APP_NAME=sweet \
TEST_ENV=qa5 \
bin/ci'
junit '**/test-reports/*.xml'
}
},
"word" : {
node("has-docker") {
git 'ssh://g...@stash.example.com/automation/word.git'
sh 'APP_NAME=word \
TEST_ENV=qa5 \
bin/ci'
junit '**/nosetests.xml'
}
}
)
}
}
}
post {
always {
deleteDir()
}
}
}
So in
[JIRA] (JENKINS-36871) JNLPProtocol4
Title: Message Title
Sam Gleske edited a comment on JENKINS-36871
Re: JNLPProtocol4
How does one confirm that JNLP4 is being used . ? I tried the latest Jenkins ver. 2.38 (weekly) and configured a JNLP slave (there's no option to configure what kind of JNLP slave).Additionally, the agent logs don't show much in the way of output confirming which JNLP protocol is even being used. Here's the full log output from the initialization of the JNLP slave.{code:none}JNLP agent connected from /REDACTED<===[JENKINS REMOTING CAPACITY]===>Slave.jar version: 3.3This is a Unix agentAgent successfully connected and online{code}So far, I'm not sure how to tell what protocol is being used.
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-36871) JNLPProtocol4
Title: Message Title Sam Gleske commented on JENKINS-36871 Re: JNLPProtocol4 How does one confirm that JNLP4 is being used. I tried the latest Jenkins ver. 2.38 (weekly) and configured a JNLP slave (there's no option to configure what kind of JNLP slave). Additionally, the agent logs don't show much in the way of output confirming which JNLP protocol is even being used. Here's the full log output from the initialization of the JNLP slave. JNLP agent connected from /REDACTED <===[JENKINS REMOTING CAPACITY]===>Slave.jar version: 3.3 This is a Unix agent Agent successfully connected and online So far, I'm not sure how to tell what protocol is being used. 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-40524) Rework agent syntax to be more extensible
Title: Message Title
Patrick Wolf commented on JENKINS-40524
Re: Rework agent syntax to be more extensible
Andrew Bayer What happens if someone does this:
agent {
dockerArgs "-v /tmp:/tmp -p 80:80"
label "foo"
}
Would this be caught in syntax check?
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-40698) Build is not triggered whether repo owner is lowercase
Title: Message Title Kamil Grabowski updated an issue Jenkins / JENKINS-40698 Build is not triggered whether repo owner is lowercase Change By: Kamil Grabowski I have a github organization named: MyOrganization and repository MyOrganization/my-repository.If I put "myorganization" (instead of "MyOrganization") as a GitHub Organization Owner then build is not triggered when one creates new pull request or a new commit .Build is triggered when I will run manually "Re-scan Organization". I think that github organization owner should be case insensitive. 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-40698) Build is not triggered whether repo owner is lowercase
Title: Message Title Kamil Grabowski updated an issue Jenkins / JENKINS-40698 Build is not triggered whether repo owner is lowercase Change By: Kamil Grabowski I have an a github organization named: MyOrganization and repository MyOrganization/my-repository.If I put "myorganization" (instead of "MyOrganization") as a GitHub Organization Owner then build is not triggered when one creates pull request.Build is triggered when I will run manually "Re-scan Organization". I think that github organization owner should be case insensitive. 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-40698) Build is not triggered whether repo owner is lowercase
Title: Message Title Kamil Grabowski created an issue Jenkins / JENKINS-40698 Build is not triggered whether repo owner is lowercase Issue Type: Bug Assignee: ben patterson Attachments: Screen Shot 2016-12-27 at 22.58.58.png Components: ghprb-plugin Created: 2016/Dec/27 10:04 PM Environment: Ubuntu Linux 14.04 64-bit Jenkins 2.38 Github Pull Request Builder 1.33.4 Priority: Minor Reporter: Kamil Grabowski I have an github organization named: MyOrganization and repository MyOrganization/my-repository. If I put "myorganization" (instead of "MyOrganization") as a GitHub Organization Owner then build is not triggered when one creates pull request. Build is triggered when I will run manually "Re-scan Organization". I think that github organization owner should be case insensitive. Add Comment
[JIRA] (JENKINS-40697) Repository connector plugin is not working
Title: Message Title Aishwarya R created an issue Jenkins / JENKINS-40697 Repository connector plugin is not working Issue Type: Bug Assignee: Unassigned Components: repository-connector-plugin Created: 2016/Dec/27 10:04 PM Priority: Critical Reporter: Aishwarya R Repositoy connector plugin not working with Nexus 3.1 or 3.2 unable to fetch the artefact versions from nexus. No versions could be resolved for groupid.artifactid Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha
[JIRA] (JENKINS-36826) Support Jenkins Pipeline for Jabber notifications
Title: Message Title Ryan Fox commented on JENKINS-36826 Re: Support Jenkins Pipeline for Jabber notifications +1 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-38293) Unable to create Jira issue using Jira plugin for jenkins
Title: Message Title Vladymyr Yuhai edited a comment on JENKINS-38293 Re: Unable to create Jira issue using Jira plugin for jenkins I have the same problem.I have Jira v. 7.0.2. and Jira plugin v.2.3 Jira connection "Validate" works fine !screenshot-1.png|thumbnail! But my build step is failingERROR: Build step failed with exceptionjava.lang.NullPointerException at hudson.plugins.jira.JiraSession.createIssue(JiraSession.java:414) at hudson.plugins.jira.JiraCreateIssueNotifier.createJiraIssue(JiraCreateIssueNotifier.java:200) at hudson.plugins.jira.JiraCreateIssueNotifier.currentBuildResultFailure(JiraCreateIssueNotifier.java:356) at hudson.plugins.jira.JiraCreateIssueNotifier.perform(JiraCreateIssueNotifier.java:155) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:45) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:720) at hudson.model.Build$BuildExecution.post2(Build.java:185) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:665) at hudson.model.Run.execute(Run.java:1745) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:404)Build step 'JIRA: Create issue' marked build as failure My project configuring: !screenshot-2.png|thumbnail! What have i done wrong? 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
[JIRA] (JENKINS-38293) Unable to create Jira issue using Jira plugin for jenkins
Title: Message Title Vladymyr Yuhai updated an issue Jenkins / JENKINS-38293 Unable to create Jira issue using Jira plugin for jenkins Change By: Vladymyr Yuhai Attachment: screenshot-2.png 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-38293) Unable to create Jira issue using Jira plugin for jenkins
Title: Message Title Vladymyr Yuhai reopened an issue Jenkins / JENKINS-38293 Unable to create Jira issue using Jira plugin for jenkins Change By: Vladymyr Yuhai Resolution: Cannot Reproduce Status: Resolved Reopened Assignee: Radek Antoniuk 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-38293) Unable to create Jira issue using Jira plugin for jenkins
Title: Message Title Vladymyr Yuhai updated an issue Jenkins / JENKINS-38293 Unable to create Jira issue using Jira plugin for jenkins Change By: Vladymyr Yuhai Attachment: screenshot-1.png 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-38293) Unable to create Jira issue using Jira plugin for jenkins
Title: Message Title Vladymyr Yuhai updated an issue Jenkins / JENKINS-38293 Unable to create Jira issue using Jira plugin for jenkins Change By: Vladymyr Yuhai Attachment: screenshot-1.png 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-38293) Unable to create Jira issue using Jira plugin for jenkins
Title: Message Title Vladymyr Yuhai commented on JENKINS-38293 Re: Unable to create Jira issue using Jira plugin for jenkins I have the same problem. I have Jira v. 7.0.2. and Jira plugin v.2.3 Jira connection "Validate" works fine But my build step is failing ERROR: Build step failed with exception java.lang.NullPointerException at hudson.plugins.jira.JiraSession.createIssue(JiraSession.java:414) at hudson.plugins.jira.JiraCreateIssueNotifier.createJiraIssue(JiraCreateIssueNotifier.java:200) at hudson.plugins.jira.JiraCreateIssueNotifier.currentBuildResultFailure(JiraCreateIssueNotifier.java:356) at hudson.plugins.jira.JiraCreateIssueNotifier.perform(JiraCreateIssueNotifier.java:155) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:45) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:720) at hudson.model.Build$BuildExecution.post2(Build.java:185) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:665) at hudson.model.Run.execute(Run.java:1745) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:404) Build step 'JIRA: Create issue' marked build as failure What have i done wrong? 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
[JIRA] (JENKINS-38293) Unable to create Jira issue using Jira plugin for jenkins
Title: Message Title Vladymyr Yuhai updated an issue Jenkins / JENKINS-38293 Unable to create Jira issue using Jira plugin for jenkins Change By: Vladymyr Yuhai Attachment: screenshot-1.png 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-40693) badMessage: 400 Bad Host header for HttpChannelOverHttp
Title: Message Title Arnaud Héritier commented on JENKINS-40693 Re: badMessage: 400 Bad Host header for HttpChannelOverHttp Maybe olamy could have some feedback ? 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-27498) Configure screen stack traces on me
Title: Message Title Arnaud Héritier commented on JENKINS-27498 Re: Configure screen stack traces on me Hi Brian Wilson I think it should be better to open a different case for your issue. This one had the component cloudformation-plugin which isn't related at all to the Fortify on Demand Uploader Plugin I cannot (sadly) clone the issue and keep all your comments (where there are the interesting informations) Could you open a new issue and copy all your informations in it please ? 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-40696) CLONE - Configure screen stack traces on me
Title: Message Title Gregg Lowrimore created an issue Jenkins / JENKINS-40696 CLONE - Configure screen stack traces on me Issue Type: Bug Assignee: Unassigned Components: jenkins-cloudformation Created: 2016/Dec/27 8:31 PM Environment: 1.605 on RHEL5 Linux Labels: jenkins Priority: Major Reporter: Gregg Lowrimore Some king of Jelly NPE exception I think. But it renders the configure screen useless, though Jenkins never crashes. Add Comment
[JIRA] (JENKINS-40696) CLONE - Configure screen stack traces on me
Title: Message Title Arnaud Héritier deleted an issue Jenkins / JENKINS-40696 CLONE - Configure screen stack traces on me 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-40695) Allow running Pipeline shared library functions on executor
Title: Message Title Owen Wood created an issue Jenkins / JENKINS-40695 Allow running Pipeline shared library functions on executor Issue Type: New Feature Assignee: Unassigned Components: workflow-cps-global-lib-plugin Created: 2016/Dec/27 8:08 PM Priority: Minor Reporter: Owen Wood New feature suggestion. Currently, all shared library functions seem to execute on the master. Allow defining some sort of mechanism to allow specifying an executor for the code execution. Some ideas: by defining this in the library code (something similar to what node(...) definitions do) via a shared library form field that allows defining the agent to run on checkbox on the shared library form that toggles whether code should be run same node as calling Pipeline block Add Comment
[JIRA] (JENKINS-40694) Allow defining CWD for Pipeline shared libraries
Title: Message Title Owen Wood created an issue Jenkins / JENKINS-40694 Allow defining CWD for Pipeline shared libraries Issue Type: New Feature Assignee: Unassigned Components: workflow-cps-global-lib-plugin Created: 2016/Dec/27 7:51 PM Priority: Minor Reporter: Owen Wood New feature suggestion. Currently shared library functions seem to use user.dir (on the master) as their current working directory (CWD). Suggesting adding a new form field to allow for specifying CWD for a shared libary definition. Add Comment
[JIRA] (JENKINS-40693) badMessage: 400 Bad Host header for HttpChannelOverHttp
Title: Message Title Oleg Nenashev commented on JENKINS-40693 Re: badMessage: 400 Bad Host header for HttpChannelOverHttp Alternative approach: Contribute backport to Jetty 9.2.x branch, which still seems to be alive: https://github.com/eclipse/jetty.project/blob/jetty-9.2.x/jetty-http/src/main/java/org/eclipse/jetty/http/HttpParser.java#L832-L838 . I am not sure they will accept it 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-40693) badMessage: 400 Bad Host header for HttpChannelOverHttp
Title: Message Title Oleg Nenashev commented on JENKINS-40693 Re: badMessage: 400 Bad Host header for HttpChannelOverHttp I was recently digging into Jetty project as a part of the research for a non-Jenkins Java server. We cannot easily upgrade to Jetty 9.3 because it EOLs the support of Java 7. If this issue really requires a fix ASAP, we need a temporary custom fork till Java 7 gets dropped in Jenkins. 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-25832) Launch multiple slaves in parallel for jobs with same node label
Title: Message Title Vinay Sharma commented on JENKINS-25832 Re: Launch multiple slaves in parallel for jobs with same node label Vikas Thakur Hi, Regarding the JVM settings : -Dhudson.model.LoadStatistics.decay=0.1 -Dhudson.model.LoadStatistics.clock=3000 Did u add these JVM settings in the jenkins.xml file or the EC2 plugin (textbox) in Jenkins ? 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-40693) badMessage: 400 Bad Host header for HttpChannelOverHttp
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-40693 badMessage: 400 Bad Host header for HttpChannelOverHttp Change By: Oleg Nenashev Issue Type: New Feature Bug 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-40693) badMessage: 400 Bad Host header for HttpChannelOverHttp
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-40693 badMessage: 400 Bad Host header for HttpChannelOverHttp Change By: Oleg Nenashev Labels: regression 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-40693) badMessage: 400 Bad Host header for HttpChannelOverHttp
Title: Message Title Oleg Nenashev commented on JENKINS-40693 Re: badMessage: 400 Bad Host header for HttpChannelOverHttp From what I see it's rather a regression than a new feature request 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-40693) badMessage: 400 Bad Host header for HttpChannelOverHttp
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-40693 badMessage: 400 Bad Host header for HttpChannelOverHttp Change By: Oleg Nenashev Component/s: core 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-40693) badMessage: 400 Bad Host header for HttpChannelOverHttp
Title: Message Title
Arnaud Héritier created an issue
Jenkins / JENKINS-40693
badMessage: 400 Bad Host header for HttpChannelOverHttp
Issue Type:
New Feature
Assignee:
Unassigned
Components:
winstone-jetty
Created:
2016/Dec/27 6:18 PM
Environment:
Jenkins 2+
Priority:
Major
Reporter:
Arnaud Héritier
Behind a reverse proxy a requests may fail with this error
WARNING o.e.jetty.util.log.JavaUtilLog#warn: badMessage: 400 Bad Host header for HttpChannelOverHttp@123456{r=0,c=false,a=IDLE,uri=/foo/bar/}
In Jenkins 2.0 Jetty was upgraded from 8.1 to 9.2 which removes AJP functionality, and also requires that if the HOST: field is used it can not be empty. KO:
GET /foo/bar HTTP/1.1\r\nHOST: \r\nConnection: Close\r\n\r\n
OK:
GET /foo/bar HTTP/1.1\r\nHOST:null \r\nConnection: Close\r\n\r\n
Current winstone version includes Jetty server 9.2.15.v20160210. The fix is in 9.3 See:
[JIRA] (JENKINS-40692) Excluded regions don't work
Title: Message Title Pepijn Schmitz created an issue Jenkins / JENKINS-40692 Excluded regions don't work Issue Type: Bug Assignee: Unassigned Components: subversion-plugin Created: 2016/Dec/27 5:57 PM Environment: Jenkins version: 1.642.1 Subversion plugin version: 1.54 Operating system: Red Hat Linux Java version: 1.8.0_72 System Properties: awt.toolkit sun.awt.X11.XToolkit com.sun.akuma.Daemon daemonized executable-war /usr/lib/jenkins/jenkins.war file.encoding UTF-8 file.encoding.pkg sun.io file.separator / guice.disable.misplaced.annotation.check true hudson.diyChunking true java.awt.graphicsenv sun.awt.X11GraphicsEnvironment java.awt.headless true java.awt.printerjob sun.print.PSPrinterJob java.class.path /usr/lib/jenkins/jenkins.war java.class.version 52.0 java.endorsed.dirs /usr/java/jdk1.8.0_72/jre/lib/endorsed java.ext.dirs /usr/java/jdk1.8.0_72/jre/lib/ext:/usr/java/packages/lib/ext java.home /usr/java/jdk1.8.0_72/jre java.io.tmpdir /tmp java.library.path /usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib java.runtime.name Java(TM) SE Runtime Environment java.runtime.version 1.8.0_72-b15 java.specification.name Java Platform API Specification java.specification.vendor Oracle Corporation java.specification.version 1.8 java.vendor Oracle Corporation java.vendor.url http://java.oracle.com/ java.vendor.url.bug http://bugreport.sun.com/bugreport/ java.version 1.8.0_72 java.vm.info mixed mode java.vm.name Java HotSpot(TM) 64-Bit Server VM java.vm.specification.name Java Virtual Machine Specification java.vm.specification.vendor Oracle Corporation java.vm.specification.version 1.8 java.vm.vendor Oracle Corporation java.vm.version 25.72-b15 JENKINS_HOME /var/lib/jenkins jna.loaded true jna.platform.library.path /usr/lib64:/lib64:/usr/lib:/lib:/usr/lib/vmware-tools/lib64/libvmGuestLibJava.so:/usr/lib/vmware-tools/lib32/libvmGuestLibJava.so:/usr/lib/vmware-tools/lib64/libvmGuestLib.so:/usr/lib/vmware-tools/lib32/libvmGuestLib.so:/usr/lib64/qt-3.3/lib:/usr/lib64/mysql:/usr/lib/vmware-tools/lib64/libDeployPkg.so:/usr/lib/vmware-tools/lib32/libDeployPkg.so jnidispatch.path /tmp/jna--1712433994/jna4536414247536192020.tmp line.separator mail.smtp.sendpartial true mail.smtps.sendpartial true os.arch amd64 os.name Linux os.version 2.6.32-642.3.1.el6.x86_64 path.separator : securerandom.source file:/dev/./urandom sun.arch.data.model 64 sun.boot.class.path /usr/java/jdk1.8.0_72/jre/lib/resources.jar:/usr/java/jdk1.8.0_72/jre/lib/rt.jar:/usr/java/jdk1.8.0_72/jre/lib/sunrsasign.jar:/usr/java/jdk1.8.0_72/jre/lib/jsse.jar:/usr/java/jdk1.8.0_72/jre/lib/jc
[JIRA] (JENKINS-28075) Want to see the LoadRunner controller execute when runing from Jenkins
Title: Message Title Yafim Kazak stopped work on JENKINS-28075 Change By: Yafim Kazak Status: In Progress Open 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-40673) Integration Tests
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40673 Re: Integration Tests Code changed in jenkins User: Martin Reinhardt Path: src/test/java/jenkins/plugins/rocketchatnotifier/rocket/RocketChatClientIT.java http://jenkins-ci.org/commit/rocketchatnotifier-plugin/603e6affd6b8de1be3d32d1b5180116868e9b9c7 Log: feat(new-rocket-api): Let integration tests respect RocketChat version (see #JENKINS-40595 and #JENKINS-40673) 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-40595) Support for new API as of RocketChat 0.48.1+
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40595 Re: Support for new API as of RocketChat 0.48.1+ Code changed in jenkins User: Martin Reinhardt Path: src/test/java/jenkins/plugins/rocketchatnotifier/rocket/RocketChatClientIT.java http://jenkins-ci.org/commit/rocketchatnotifier-plugin/603e6affd6b8de1be3d32d1b5180116868e9b9c7 Log: feat(new-rocket-api): Let integration tests respect RocketChat version (see #JENKINS-40595 and #JENKINS-40673) 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-32560) jira-plugin generating message in the wrong ticket
Title: Message Title Radek Antoniuk commented on JENKINS-32560 Re: jira-plugin generating message in the wrong ticket Still thinking about it... could this be anyhow related to JENKINS-32884? 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-40673) Integration Tests
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40673 Re: Integration Tests Code changed in jenkins User: Martin Reinhardt Path: src/main/java/jenkins/plugins/rocketchatnotifier/rocket/LegacyRocketChatClient.java src/test/java/jenkins/plugins/rocketchatnotifier/rocket/RocketChatClientIT.java http://jenkins-ci.org/commit/rocketchatnotifier-plugin/aa9614f28bf253cd7c2216c54ce559dd0c7d196e Log: feat(new-rocket-api): Let integration tests respect RocketChat version (see #JENKINS-40595 and #JENKINS-40673) 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-40595) Support for new API as of RocketChat 0.48.1+
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40595 Re: Support for new API as of RocketChat 0.48.1+ Code changed in jenkins User: Martin Reinhardt Path: src/main/java/jenkins/plugins/rocketchatnotifier/rocket/LegacyRocketChatClient.java src/test/java/jenkins/plugins/rocketchatnotifier/rocket/RocketChatClientIT.java http://jenkins-ci.org/commit/rocketchatnotifier-plugin/aa9614f28bf253cd7c2216c54ce559dd0c7d196e Log: feat(new-rocket-api): Let integration tests respect RocketChat version (see #JENKINS-40595 and #JENKINS-40673) 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-40690) One of files fails with SdkClientException: Couldn't initialize a SAX driver to create an XMLReader
Title: Message Title Kamil P commented on JENKINS-40690 Re: One of files fails with SdkClientException: Couldn't initialize a SAX driver to create an XMLReader There is an interesting observation in JENKINS-19725 about the 16M size limit. 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-40393) Internationalize all the error messages in Declarative
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40393 Re: Internationalize all the error messages in Declarative Code changed in jenkins User: Andrew Bayer Path: pipeline-model-api/src/main/java/org/jenkinsci/plugins/pipeline/modeldefinition/ast/ModelASTMethodCall.java pipeline-model-api/src/main/java/org/jenkinsci/plugins/pipeline/modeldefinition/ast/ModelASTStep.java pipeline-model-api/src/main/resources/org/jenkinsci/plugins/pipeline/modeldefinition/ast/Messages.properties pipeline-model-definition/src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/parser/JSONParser.groovy pipeline-model-definition/src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/parser/ModelParser.groovy pipeline-model-definition/src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/parser/Parser.groovy pipeline-model-definition/src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/validator/ModelValidatorImpl.groovy pipeline-model-definition/src/main/resources/org/jenkinsci/plugins/pipeline/modeldefinition/Messages.properties pipeline-model-definition/src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/AbstractModelDefTest.java pipeline-model-definition/src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/DeclarativeLinterCommandTest.java pipeline-model-definition/src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/ValidatorTest.java pipeline-model-definition/src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/WhenStageTest.java pipeline-model-definition/src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/endpoints/ModelConverterActionTest.java pipeline-model-definition/src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/parser/GroovyShellDecoratorImplTest.java pipeline-model-definition/src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/parser/ModelParserTest.java http://jenkins-ci.org/commit/pipeline-model-definition-plugin/3f75171a4031d63cca251d0c05b34e480df746bb Log: Merge pull request #71 from abayer/i18n [FIXED JENKINS-40393] i18n for validation messages Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-40691) Do not start new VMs when there're not enough resources available
Title: Message Title Anna Tikhonova created an issue Jenkins / JENKINS-40691 Do not start new VMs when there're not enough resources available Issue Type: Improvement Assignee: Roman Kulikov Components: parallels-desktop-plugin Created: 2016/Dec/27 5:14 PM Environment: Jenkins ver. 1.651.1, parallels-desktop-plugin 0.3 Priority: Minor Reporter: Anna Tikhonova As of ver 0.3, parallels-desktop-plugin provisions as many VMs as Jenkins master requests at a time. This results in multiple VMs running simultaneously despite their configuration, which: a) Will be slower than expected b) Might result in something like described in JENKINS-40685 (it happened exactly when Parallels Desktop was starting up two VMs with the total memory greater than the host memory – the hardcoded timeout wasn't enough) The suggestion is to implement a pre-provisioning check that the total resources required by the multiple VMs to be provisioned are not greater that what the host has. The check could be optional (a checkbox in Cloud configuration).
[JIRA] (JENKINS-40690) One of files fails with SdkClientException: Couldn't initialize a SAX driver to create an XMLReader
Title: Message Title
Kamil P updated an issue
Jenkins / JENKINS-40690
One of files fails with SdkClientException: Couldn't initialize a SAX driver to create an XMLReader
Change By:
Kamil P
It is run from jenkinsfile {code}step([$class: 'S3BucketPublisher', consoleLogLevel: 'INFO', dontWaitForConcurrentBuildCompletion: true, entries: [[ bucket: 'mybucket', excludedFile: '', flatten: false, gzipFiles: true, keepForever: false, managedArtifacts: true, noUploadOnFailure: false, selectedRegion: 'eu-central-1', showDirectlyInBrowser: false, sourceFile: 'artifacts/**/*.*', storageClass: 'STANDARD', uploadFromSlave: false, useServerSideEncryption: false]], pluginFailureResultConstraint: 'FAILURE', profileName: 'jenkins', userMetadata: []]){code}Some files are uploaded sucessfuly to s3 bucket, but then it keep failing on one of the files. with the following error{panel:title=Jenkins console output}ERROR: Failed to upload filescom.amazonaws.SdkClientException: Couldn't initialize a SAX driver to create an XMLReader at com.amazonaws.services.s3.model.transform.XmlResponsesSaxParser.(XmlResponsesSaxParser.java:113) at com.amazonaws.services.s3.model.transform.Unmarshallers$InitiateMultipartUploadResultUnmarshaller.unmarshall(Unmarshallers.java:237) at com.amazonaws.services.s3.model.transform.Unmarshallers$InitiateMultipartUploadResultUnmarshaller.unmarshall(Unmarshallers.java:234) at com.amazonaws.services.s3.internal.S3XmlResponseHandler.handle(S3XmlResponseHandler.java:62) at com.amazonaws.services.s3.internal.ResponseHeaderHandlerChain.handle(ResponseHeaderHandlerChain.java:44) at com.amazonaws.services.s3.internal.ResponseHeaderHandlerChain.handle(ResponseHeaderHandlerChain.java:30) at com.amazonaws.http.response.AwsResponseHandlerAdapter.handle(AwsResponseHandlerAdapter.java:70) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.handleResponse(AmazonHttpClient.java:1444) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeOneRequest(AmazonHttpClient.java:1151) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeHelper(AmazonHttpClient.java:964) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.doExecute(AmazonHttpClient.java:676) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeWithTimer(AmazonHttpClient.java:650) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.execute(AmazonHttpClient.java:633) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.access$300(AmazonHttpClient.java:601) at com.amazonaws.http.AmazonHttpClient$RequestExecutionBuilderImpl.execute(AmazonHttpClient.java:583) at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:447) at com.amazonaws.services.s3.AmazonS3Client.invoke(AmazonS3Client.java:4137) at
[JIRA] (JENKINS-40690) One of files fails with SdkClientException: Couldn't initialize a SAX driver to create an XMLReader
Title: Message Title Kamil P created an issue Jenkins / JENKINS-40690 One of files fails with SdkClientException: Couldn't initialize a SAX driver to create an XMLReader Issue Type: Bug Assignee: Alexander A Components: s3-plugin Created: 2016/Dec/27 5:11 PM Environment: jenkins 2.19.4, S3 Publisher Plugin 0.10.11 Priority: Major Reporter: Kamil P It is run from jenkinsfile step([$class: 'S3BucketPublisher', consoleLogLevel: 'INFO', dontWaitForConcurrentBuildCompletion: true, entries: [[ bucket: 'mybucket', excludedFile: '', flatten: false, gzipFiles: true, keepForever: false, managedArtifacts: true, noUploadOnFailure: false, selectedRegion: 'eu-central-1', showDirectlyInBrowser: false, sourceFile: 'artifacts/**/*.*', storageClass: 'STANDARD', uploadFromSlave: false, useServerSideEncryption: false]], pluginFailureResultConstraint: 'FAILURE', profileName: 'jenkins', userMetadata: []]) Some files are uploaded sucessfuly to s3 bucket, but then it keep failing on one of the files. with the following error
[JIRA] (JENKINS-40683) Create functional tests for some provided tokens
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40683 Re: Create functional tests for some provided tokens Code changed in jenkins User: Evaristo Gutiérrez Path: src/test/java/org/jenkinsci/plugins/tokenmacro/impl/BuildNumberMacroTest.java src/test/java/org/jenkinsci/plugins/tokenmacro/impl/JenkinsUrlMacroTest.java src/test/java/org/jenkinsci/plugins/tokenmacro/impl/ProjectNameMacroTest.java src/test/java/org/jenkinsci/plugins/tokenmacro/impl/ProjectUrlMacroTest.java http://jenkins-ci.org/commit/token-macro-plugin/553232ec945f67c56f010909b25debcbdafe435c Log: JENKINS-40683 Create functional tests for BUILD_NUMBER, JENKINS_URL, PROJECT_NAME and PROJECT_URL tokens. (#27) 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-40683) Create functional tests for some provided tokens
Title: Message Title Evaristo Gutierrez commented on JENKINS-40683 Re: Create functional tests for some provided tokens Alex Earl after putting it in Review you mean? 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-40683) Create functional tests for some provided tokens
Title: Message Title Alex Earl commented on JENKINS-40683 Re: Create functional tests for some provided tokens Why was this issue not assigned to the plugin maintainer? 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-40524) Rework agent syntax to be more extensible
Title: Message Title
Andrew Bayer commented on JENKINS-40524
Re: Rework agent syntax to be more extensible
Peter Leibiger So I'm not a big fan of that - I definitely understand the thinking, but given that label always just has the one value, it feels like nesting it inside a closure is a bit overly verbose. We're committed to continuing to support agent any, which means "run on any agent" (while agent none means "don't run in a node block at all and leave that up to individual stages"), so I don't think we'd get anything from nesting label further. I've been pondering this for the last week and think I'm going to go with the current PR's approach - i.e.,
agent {
label "foo"
}
agent {
docker "httpd:2.4.12"
dockerArgs "-v /tmp:/tmp -p 80:80"
label "foo"
// the below would be for things like private registry, kubernetes pod config, whatever
someComplicatedOption {
optA "banana"
optB "monkey"
}
}
agent {
dockerfile "true"
dockerArgs "-v /tmp:/tmp -p 80:80"
label "foo"
}
It's not ideal, but it's the easiest to do by far. I completely get the confusion of label nested inside a docker block, but to do a docker block with a separate label definition would actually require a fairly drastic change to how the DeclarativeAgent classes work, since we'd go from having just one DeclarativeAgent (i.e., one of https://github.com/jenkinsci/pipeline-model-definition-plugin/tree/master/pipeline-model-definition/src/main/java/org/jenkinsci/plugins/pipeline/modeldefinition/agent/impl, identified by a key) to having to combine multiple, which is...messy. I'm gonna sleep on it one more night and see if an idea comes to me for a good implementation of combining them, but I don't think that's likely to happen. =)
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-28667) Memory usage of jnlp slave
Title: Message Title Oleg Nenashev resolved as Incomplete Closing it as Incomplete since there is not enough information to diagnose && there were many related fixes && I do not see such behavior on my instances Jenkins / JENKINS-28667 Memory usage of jnlp slave Change By: Oleg Nenashev Status: Open Resolved Resolution: Incomplete 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-issu
[JIRA] (JENKINS-34322) Graceful error reporting if build agent runs unsupported version of Java
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-34322 Graceful error reporting if build agent runs unsupported version of Java Change By: Oleg Nenashev Issue Type: Bug Improvement 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-33428) Unable to kill JNLP process
Title: Message Title Oleg Nenashev commented on JENKINS-33428 Re: Unable to kill JNLP process So the thread waits infinitely if it cannot download the JNLP file due to whatever reason. Smells lie a bug in the core's process termination logic (or in remoting) 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-33450) xUnit compatibility with NUnit 3
Title: Message Title
Lorenzo Solano Martinez commented on JENKINS-33450
Re: xUnit compatibility with NUnit 3
Hi Will Appleby and Jason Carlberg, I did a simmilar trick, as follow: From https://github.com/nunit/nunit-console on branch release/3.5 I found the following test scenario
Name-space: NUnit.ConsoleRunner.Tests
Test Class: CommandLineTests
Scenario: ResultOptionWithFilePathAndFormat()
Options: ConsoleOptions options = new ConsoleOptions("tests.dll", "-result:results.xml;format=nunit2");
After changing my NUnit run step on Jenkins from old v2 console runner to V3 "%NUNIT3_HOME%\nunit3-console.exe" NUnitTests.nunit /config=%MSBuildConfiguration% --framework=net-4.5 -result:TestResult.xml;format=nunit2 The last option is what did the trick: -result:TestResult.xml;format=nunit2 , that way you tell the console runner to write the output in the V2 format and also to use the legacy (v2 default) name TestResult.xml. I'm also waiting to use a future release of the xUnit plugin with support for NUnit 3.x. I believe that the conversion process is a little bit slower for the v3 console runner. Environment:
Windows 2012 R2
Jenkins: 1.651.1
xUnit Plugin: 1.102
NUnit: 3.5 (framework and console runner with v2 driver / plugin)
Add Comment
[JIRA] (JENKINS-37559) cannot abort shell scripts on 64-bit Solaris
Title: Message Title SCM/JIRA link daemon commented on JENKINS-37559 Re: cannot abort shell scripts on 64-bit Solaris Code changed in jenkins User: Oleg Nenashev Path: core/src/main/java/hudson/util/ProcessTree.java core/src/main/java/hudson/util/jna/GNUCLibrary.java http://jenkins-ci.org/commit/jenkins/b4cc77011e8ea90a4c4f924e10cfa08f45ce1f34 Log: Revert "[FIXED JENKINS-37559] - Fix ProcessTree.java on Solaris with 64-bit JVM" 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-36792) Jenkins Fails To Start After Update
Title: Message Title Oleg Nenashev commented on JENKINS-36792 Re: Jenkins Fails To Start After Update IMHO we cannot diagnose it in the current state. I do not see the follow-up in mailing lists 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-37034) Deadlock in hudson.model.Executor
Title: Message Title Oleg Nenashev commented on JENKINS-37034 Re: Deadlock in hudson.model.Executor Pavel Janoušek please provide as full thread dump. It's not possible to analyze deadlocks only by a single thread trace. It would be also useful to know your Jenkins version. If it's reported to something below 1.625, maybe it worth to reproduce the issue on higher versions. 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-37112) Windows batch command only executing 1st line from list of commands given in bat file
Title: Message Title Oleg Nenashev commented on JENKINS-37112 Re: Windows batch command only executing 1st line from list of commands given in bat file Cannot reproduce the issue. Would be useful to have some pointers like Jenkins version at least 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-39179) All builds hang, JNA load deadlock on Windows slave
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-39179 All builds hang, JNA load deadlock on Windows slave Change By: Oleg Nenashev Component/s: remoting Component/s: slave-status-plugin 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-19465) Slave hangs while being launched
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-19465 Slave hangs while being launched Change By: Oleg Nenashev Component/s: remoting Component/s: core 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-39880) Jenkins agents should offer better Diagnostics remote operation failures due to JDK-8017777
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-39880 Jenkins agents should offer better Diagnostics remote operation failures due to JDK-801 Change By: Oleg Nenashev Component/s: core 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-40688) secrets "shared-secrets" not found
Title: Message Title
fii fii commented on JENKINS-40688
Re: secrets "shared-secrets" not found
Sure ... I am attempting to launch a slave in jenkins following this https://github.com/carlossg/jenkins-kubernetes-plugin but when we add this (below) the nodes just stay offline. podTemplate(label: 'mypod', containers: [ containerTemplate(name: 'maven', image: 'maven:3.3.9-jdk-8-alpine', ttyEnabled: true, command: 'cat'), containerTemplate(name: 'golang', image: 'golang:1.6.3-alpine', ttyEnabled: true, command: 'cat') ], volumes: [secretVolume(secretName: 'shared-secrets', mountPath: '/etc/shared-secrets')]) { node ('mypod') { stage 'Get a Maven project' git 'https://github.com/jenkinsci/kubernetes-plugin.git' container('maven') { stage 'Build a Maven project' sh 'mvn clean install' } stage 'Get a Golang project' git url: 'https://github.com/hashicorp/terraform.git' container('golang') { stage 'Build a Go project' sh """ mkdir -p /go/src/github.com/hashicorp ln -s `pwd` /go/src/github.com/hashicorp/terraform cd /go/src/github.com/hashicorp/terraform && make core-dev """ } } } *Error messages from Jenkins: *Agent kubernetes-66ef3c8e8b764a6d88941b21b74d03e8-34a6491ff5f (kubernetes-66ef3c8e8b764a6d88941b21b74d03e8) This agent is offline because Jenkins failed to launch the agent process on it. See log for more details Connect agent to Jenkins one of these ways: launch agent Launch agent from browser Run from agent command line: javaws http://jenkins.default.104.155.119.6.nip.io/computer/kubernetes-66ef3c8e8b764a6d88941b21b74d03e8-34a6491ff5f/slave-agent.jnlp Or if the agent is headless: java -jar slave.jar -jnlpUrl http://jenkins.default.104.155.119.6.nip.io/computer/kubernetes-66ef3c8e8b764a6d88941b21b74d03e8-34a6491ff5f/slave-agent.jnlp Created by SYSTEM Labels mypod Projects tied to kubernetes-66ef3c8e8b764a6d88941b21b74d03e8-34a6491ff5f And from the kubernetes : FirstSeen LastSeen Count From SubobjectPath Type Reason Message - - - -- --- 6m 6m 1 {default-scheduler } Normal Scheduled Successfully assigned kubernetes-36906361c1934228b1c68073cd1b13ac-1fb1e064aea to gke-jenkins-default-pool-272e742d-c9pl 6m 32s 11 {kubelet gke-jenkins-default-pool-272e742d-c9pl} Warning FailedMount MountVolume.SetUp failed for volume "kubernetes.io/secret/8e16eade-cc44-11e6-bab0-42010a84004e-volume-0" (spec.Name: "volume-0") pod "8e16eade-cc44-11e6-bab0-42010a84004e" (UID: "8e16eade-cc44-11e6-bab0-42010a84004e") with: secrets "shared-secrets" not found 4m 15s 3 {kubelet gke-jenkins-default-pool-272e742d-c9pl} Warning FailedMount Unable to mount volumes for pod "kubernetes-36906361c1934228b1c68073cd1b13ac-1fb1e064aea_default(8e16eade-cc44-11e6-bab0-42010a84004e)": timeout expired waiting for volumes to attach/mount for pod "kubernetes-36906361c1934228b1c68073cd1b13ac-1fb1e064aea"/"default". list of unattached/unmounted volumes=[volume-0] 4m 15s 3 {kubelet gke-jenkins-default-pool-272e742d-c9pl} Warning FailedSync Error syncing pod, skipping: timeout expired waiting for volumes to attach/mount for pod "kubernetes-36906361c1934228b1c68073cd1b13ac-1fb1e064aea"/"default". list of unattached/unmounted volumes=[volume-0] [fii@laptop ~]$ kubectl describe pod kubernetes-36906361c1934228b1c68073cd1b13ac-1fb1e064aea Error from server: pods "kubernetes-36906361c1934228b1c68073cd1b13ac-1fb1e064aea" not found
[JIRA] (JENKINS-27251) windows slaves disconnect during build
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-27251 windows slaves disconnect during build Change By: Oleg Nenashev Component/s: remoting Component/s: core 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-29641) JNLP slave agent on Mac disconnects very often
Title: Message Title Oleg Nenashev assigned an issue to Oleg Nenashev Jenkins / JENKINS-29641 JNLP slave agent on Mac disconnects very often Change By: Oleg Nenashev Assignee: Oleg Nenashev 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-29641) JNLP slave agent on Mac disconnects very often
Title: Message Title Oleg Nenashev commented on JENKINS-29641 Re: JNLP slave agent on Mac disconnects very often Smells like a remoting issue 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-29641) JNLP slave agent on Mac disconnects very often
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-29641 JNLP slave agent on Mac disconnects very often Change By: Oleg Nenashev Component/s: remoting Component/s: core 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-30039) Regression in queue control in Jenkins 1.607: Build are executed concurrently although "Execute concurrent builds if necessary" is not ticked
Title: Message Title Oleg Nenashev resolved as Fixed The issues with Queue behavior have been fixed by 1.625.x. There are known and fixed issues, which were leading to this behavior. So IMHO it makes sense to just close this ticket Jenkins / JENKINS-30039 Regression in queue control in Jenkins 1.607: Build are executed concurrently although "Execute concurrent builds if necessary" is not ticked Change By: Oleg Nenashev Status: Reopened Resolved Resolution: Fixed 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 G
[JIRA] (JENKINS-30211) Installation error: Could not initialize class com.sun.jna.Pointer
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-30211 Installation error: Could not initialize class com.sun.jna.Pointer Change By: Oleg Nenashev Labels: jna stapler 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-40685) Operation timed out when launching VM slave
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40685 Re: Operation timed out when launching VM slave Code changed in jenkins User: Roman Kulikov Path: src/main/java/com/parallels/desktopcloud/ParallelsDesktopCloud.java src/main/java/com/parallels/desktopcloud/ParallelsDesktopConnectorSlaveComputer.java http://jenkins-ci.org/commit/parallels-desktop-plugin/eee89ab98759f9f75d0802274b76898d3a1a Log: Fix job hanging on offline VM slave Just don't create node object during provisioning if VM start failed or IP address was not obtained. Let Jenkins find better executor for this job. Bug #JENKINS-40685 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-40685) Operation timed out when launching VM slave
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40685 Re: Operation timed out when launching VM slave Code changed in jenkins User: Roman Kulikov Path: src/main/java/com/parallels/desktopcloud/ParallelsDesktopConnectorSlaveComputer.java http://jenkins-ci.org/commit/parallels-desktop-plugin/2b4a832e5a610abb2b55bc47f057086a4cccf18d Log: Wait for VM IP address for 3 minutes Seems large VM on MacMini may resume for 2-3 minutes. Bug #JENKINS-40685 Compare: https://github.com/jenkinsci/parallels-desktop-plugin/compare/e7afe43af90e...2b4a832e5a61 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-30211) Installation error: Could not initialize class com.sun.jna.Pointer
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-30211 Installation error: Could not initialize class com.sun.jna.Pointer Change By: Oleg Nenashev Labels: stapler 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-40688) secrets "shared-secrets" not found
Title: Message Title Carlos Sanchez commented on JENKINS-40688 Re: secrets "shared-secrets" not found can you provide more information? 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-30535) Jenkins logged in user info
Title: Message Title Oleg Nenashev resolved as Not A Defect Not a defect && more than one year old. The behavior is valid since jobs do not receive context by default. Plugins like Authorize Project plugin may help Jenkins / JENKINS-30535 Jenkins logged in user info Change By: Oleg Nenashev Status: Open Resolved Resolution: Not A Defect 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 jenkinsc
[JIRA] (JENKINS-40688) secrets "shared-secrets" not found
Title: Message Title Carlos Sanchez updated an issue Jenkins / JENKINS-40688 secrets "shared-secrets" not found Change By: Carlos Sanchez Summary: Jenkins Kubernetes Plugin secrets "shared-secrets" not found 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-32958) EmptyStackException from Items.getCanonicalName when deleting item with Parameterized Trigger installed
Title: Message Title Oleg Nenashev resolved as Fixed Jenkins / JENKINS-32958 EmptyStackException from Items.getCanonicalName when deleting item with Parameterized Trigger installed Change By: Oleg Nenashev Status: Open Resolved Resolution: Fixed 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-32958) EmptyStackException from Items.getCanonicalName when deleting item with Parameterized Trigger installed
Title: Message Title Oleg Nenashev commented on JENKINS-32958 Re: EmptyStackException from Items.getCanonicalName when deleting item with Parameterized Trigger installed Actual issue stacktrace: Caused by: java.util.EmptyStackException at java.util.Stack.peek(Stack.java:102) at java.util.Stack.pop(Stack.java:84) at hudson.model.Items.getCanonicalName(Items.java:138) at hudson.plugins.parameterizedtrigger.BuildTriggerConfig.onDeleted(BuildTriggerConfig.java:526) at hudson.plugins.parameterizedtrigger.Plugin$RenameListener.onDeleted(Plugin.java:89) at com.cloudbees.hudson.plugins.folder.Folder.onDeleted(Folder.java:587) at com.cloudbees.hudson.plugins.folder.Folder.onDeleted(Folder.java:122) at hudson.model.AbstractItem.invokeOnDeleted(AbstractItem.java:525) at hudson.model.AbstractItem.delete(AbstractItem.java:512) at hudson.model.Job.delete(Job.java:618) at com.cloudbees.hudson.plugins.folder.Folder.performDelete(Folder.java:559) at hudson.model.AbstractItem.delete(AbstractItem.java:509) at hudson.model.AbstractItem.doDoDelete(AbstractItem.java:486) Oliver Gondža fixed it in jenkins-1.624 (https://github.com/jenkinsci/jenkins/pull/1780) 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 fro
[JIRA] (JENKINS-34029) Build Queue Items disappears and
Title: Message Title Oleg Nenashev commented on JENKINS-34029 Re: Build Queue Items disappears and Does it still happen in newer versions? there were several fixes around the Queue Snapshoting mechanism since 1.642, so likely the issue has been fixed 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-36155) windows remote slaves don't always come back online
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-36155 windows remote slaves don't always come back online Change By: Oleg Nenashev Component/s: remoting 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-36155) windows remote slaves don't always come back online
Title: Message Title Oleg Nenashev commented on JENKINS-36155 Re: windows remote slaves don't always come back online It's likely a remoting issue 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.
