[JIRA] (JENKINS-56785) default git checkout is not working while creating pipeline jobs
Title: Message Title Mohit Saraf created an issue Jenkins / JENKINS-56785 default git checkout is not working while creating pipeline jobs Issue Type: Bug Assignee: Unassigned Attachments: git-clone-issue.PNG, pipeline-definition.PNG Components: pipeline Created: 2019-03-28 05:04 Priority: Critical Reporter: Mohit Saraf Hi Team, we are running Jenkins master(2.164.1) in a docker container. When we select pipeline definition as pipeline script from scm and give the repository url and credentials, the job fails with the below error. we have already tried the basic troubleshooting by checking git path and other type of jobs are able to checkout the code. please check and advise. ERROR: Error cloning remote repo 'origin' hudson.plugins.git.GitException: Could not init /amp/jenkins/jenkins_home/workspace/A0-BuildTeam/repository/jenkins-pipeline@script at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$5.execute(CliGitAPIImpl.java:787) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:579) at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1146) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1186) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:120) at org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:144) at org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:67) at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:293) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429) Caused by: hudson.plugins.git.GitException: Error performing command: git init /amp/jenkins/jenkins_home/workspace/A0-BuildTeam/repository/jenkins-pipeline@script at
[JIRA] (JENKINS-55553) Active flag in jenkins build engine gets de-activated
Title: Message Title Lakshmi Narasimhan Vaikuntam commented on JENKINS-3 Re: Active flag in jenkins build engine gets de-activated This issue can happen if the credentials used in the engine in RTC side for Jenkins is incorrect or it has expired. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41104) Cannot get source branch in PR build in Bitbucket team project
Title: Message Title Joe Pea commented on JENKINS-41104 Re: Cannot get source branch in PR build in Bitbucket team project Figured it out. I set the `Discover branches Strategy` to `only branches that are filed as PRs`, and removed the `discover pull requests` options. Now it builds straight from my pull request branches, exactly like I wanted. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56647) Log audit event for node updates
Title: Message Title Aarthi Rajaraman updated JENKINS-56647 Jenkins / JENKINS-56647 Log audit event for node updates Change By: Aarthi Rajaraman Status: In Review Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56641) Log audit event for item updates
Title: Message Title Aarthi Rajaraman updated JENKINS-56641 Jenkins / JENKINS-56641 Log audit event for item updates Change By: Aarthi Rajaraman Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56642) Log audit event for copied items
Title: Message Title Aarthi Rajaraman updated JENKINS-56642 Jenkins / JENKINS-56642 Log audit event for copied items Change By: Aarthi Rajaraman Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56644) Log audit event for deleted items
Title: Message Title Aarthi Rajaraman updated JENKINS-56644 Jenkins / JENKINS-56644 Log audit event for deleted items Change By: Aarthi Rajaraman Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56640) Log audit event for item creation
Title: Message Title Aarthi Rajaraman updated JENKINS-56640 Jenkins / JENKINS-56640 Log audit event for item creation Change By: Aarthi Rajaraman Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38027) withMaven disabled AnsiColorBuildWrapper
Title: Message Title Sourigna Phetsarath edited a comment on JENKINS-38027 Re: withMaven disabled AnsiColorBuildWrapper Was the fix ever released? If you so, what version was it in? Thank you. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38027) withMaven disabled AnsiColorBuildWrapper
Title: Message Title Sourigna Phetsarath commented on JENKINS-38027 Re: withMaven disabled AnsiColorBuildWrapper Was the fix ever released? If you what version was it in? Thank you. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56756) Jenkins Azure Credentials Plugin (Managed Service Identity)
Title: Message Title Jie Shen commented on JENKINS-56756 Re: Jenkins Azure Credentials Plugin (Managed Service Identity) Harmit Rai, what is your scenario to use "User-assigned Managed Service Identity" in your pipeline? Indeed, this type of credential is now mainly used by our other plugins to create resources. So we do not expose it in the pipeline. For the deprecated thing, it used to request token from localhost which is deprecated. So we change it to fetch the token from the IMDS endpoint, details at https://docs.microsoft.com/en-us/azure/active-directory/managed-identities-azure-resources/overview#how-a-system-assigned-managed-identity-works-with-an-azure-vm . We will still support Managed Service Identity. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (TEST-112) Issue for testing purpose so do not mind
Title: Message Title Olivier Lamy commented on TEST-112 Re: Issue for testing purpose so do not mind pipeline step comment Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (TEST-112) Issue for testing purpose so do not mind
Title: Message Title Olivier Lamy commented on TEST-112 Re: Issue for testing purpose so do not mind SUCCESS: Integrated in Jenkins build foo-fs #14 (See http://localhost:8080/job/foo-fs/14/) TEST-112 test olamy (noreply: 28/03/19 11:25 AM https://github.com/olamy/foo/commit/c3fc4587b1d055ade8ae106e5181d6a2cab9f846) (edit) Jenkinsfile Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41104) Cannot get source branch in PR build in Bitbucket team project
Title: Message Title Joe Pea commented on JENKINS-41104 Re: Cannot get source branch in PR build in Bitbucket team project Hello, how can we use the original branch for pull request builds, instead of the PR-XXX branches? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56747) Error: ERR_SSL_VERSION_OR_CIPHER_MISMATCH
Title: Message Title Olivier Lamy commented on JENKINS-56747 Re: Error: ERR_SSL_VERSION_OR_CIPHER_MISMATCH java version? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43693) multibranchPipelineJob overrides old branch indexing sources
Title: Message Title Ray Kivisto commented on JENKINS-43693 Re: multibranchPipelineJob overrides old branch indexing sources Should this documentation be updated to include setting the id? https://jenkinsci.github.io/job-dsl-plugin/#path/multibranchPipelineJob Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43194) Lightweight checkout for PR merge jobs
Title: Message Title Liam Newman commented on JENKINS-43194 Re: Lightweight checkout for PR merge jobs I've released a beta release of this change in v2.4.6-beta-1: This is not production ready but anyone wanting to test it and give feedback would be appreciated. It is on the experimental update site. Also: https://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/github-branch-source/2.4.6-beta-1/github-branch-source-2.4.6-beta-1.hpi Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54910) Could not able to Build Azure Function APP using MSBuild Plugin
Title: Message Title Lionel Cabasson commented on JENKINS-54910 Re: Could not able to Build Azure Function APP using MSBuild Plugin Hello, This is not plugin related issue. You are probably trying to build a csproj file with an older version of MSBuild. Updatety the plugin configuration in Jenkins to use the latest MSBuild version to solve this issue. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46094) "Checkout over SSH" fails the build since it still uses HTTPS urls
Title: Message Title Liam Newman updated JENKINS-46094 Jenkins / JENKINS-46094 "Checkout over SSH" fails the build since it still uses HTTPS urls Change By: Liam Newman Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46094) "Checkout over SSH" fails the build since it still uses HTTPS urls
Title: Message Title Liam Newman commented on JENKINS-46094 Re: "Checkout over SSH" fails the build since it still uses HTTPS urls Published 2.4.5 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56767) Unexpected exception occurred while performing online-node command
Title: Message Title Chance Davies commented on JENKINS-56767 Re: Unexpected exception occurred while performing online-node command Please note: My company has recommended I remove the logs which were originally attached to this bug. I can still provide specifics and logs which do not contain system names or IPs upon request. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45664) blue-ocean parallel streams are not showing up red on a stream failure
Title: Message Title karthik paidi updated an issue Jenkins / JENKINS-45664 blue-ocean parallel streams are not showing up red on a stream failure Change By: karthik paidi Attachment: samplescript Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45664) blue-ocean parallel streams are not showing up red on a stream failure
Title: Message Title karthik paidi updated an issue Jenkins / JENKINS-45664 blue-ocean parallel streams are not showing up red on a stream failure Change By: karthik paidi Attachment: Screen Shot 2017-07-19 at 10.46.39 AM.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56674) In case of execute withDockerContainer inside withDockerCotainer env variables is not masked
Title: Message Title Jesse Glick updated JENKINS-56674 Jenkins / JENKINS-56674 In case of execute withDockerContainer inside withDockerCotainer env variables is not masked Change By: Jesse Glick Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54018) NoClassDefFoundError: Lhudson/tools/JDKInstaller when JDK Tools plugin is uninstalled
Title: Message Title Ramon Leon commented on JENKINS-54018 Re: NoClassDefFoundError: Lhudson/tools/JDKInstaller when JDK Tools plugin is uninstalled I agree we need to document it better. I will create a new task to do that, with a different title, description and priority. I will close this task as the reason for its creation is clarified. For the record, the list of plugins detached and the version when it happened is: https://github.com/jenkinsci/jenkins/blob/a78312ea0f4ba28f8bc81220c6d7c0dfa72a67df/core/src/main/resources/jenkins/split-plugins.txt Feel free to participate or follow the new task. Thank you. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49131) Steps are not shown up in Blue Ocean when one of parallel stages is skipped due to "when" condition
Title: Message Title Chris Ladd updated an issue Jenkins / JENKINS-49131 Steps are not shown up in Blue Ocean when one of parallel stages is skipped due to "when" condition Change By: Chris Ladd Environment: Jenkins ver. 2.89.3Blueocean 1.4.0Windows Server 2012 R2 Jenkins 2.138.3Blue Ocean 1.14.0Linux Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49131) Steps are not shown up in Blue Ocean when one of parallel stages is skipped due to "when" condition
Title: Message Title Chris Ladd commented on JENKINS-49131 Re: Steps are not shown up in Blue Ocean when one of parallel stages is skipped due to "when" condition I'm seeing this with Jenkins 2.138.3 and Blue Ocean 1.14.0 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49131) Steps are not shown up in Blue Ocean when one of parallel stages is skipped due to "when" condition
Title: Message Title Chris Ladd updated an issue Jenkins / JENKINS-49131 Steps are not shown up in Blue Ocean when one of parallel stages is skipped due to "when" condition Change By: Chris Ladd Priority: Major Critical Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56674) In case of execute withDockerContainer inside withDockerCotainer env variables is not masked
Title: Message Title Jesse Glick started work on JENKINS-56674 Change By: Jesse Glick Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56674) In case of execute withDockerContainer inside withDockerCotainer env variables is not masked
Title: Message Title Jesse Glick assigned an issue to Jesse Glick Jenkins / JENKINS-56674 In case of execute withDockerContainer inside withDockerCotainer env variables is not masked Change By: Jesse Glick Assignee: Jesse Glick Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55215) Log from cmake/ctest steps isn't fully captured on OsX
Title: Message Title
Martin Weber commented on JENKINS-55215
Re: Log from cmake/ctest steps isn't fully captured on OsX
I tried to reproduce this on a remote Linux agent by generationg lots of output. Pipeline script:
node('linux') {
timestamps {
stage('all') {
echo 'Hello World'
sh label: 'ls', script: 'ls -lgGR /bin /lib /lib64 /opt /usr'
}
}
}
Unfortunately, I could not reproduce the issue. Could you try to runs the script on an OSX agent to verify whether it is related to cmakebuilder or to pipeline?
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55215) Log from cmake/ctest steps isn't fully captured on OsX
Title: Message Title
Martin Weber edited a comment on JENKINS-55215
Re: Log from cmake/ctest steps isn't fully captured on OsX
I tried to reproduce this on a remote Linux agent by generationg generating lots of output.Pipeline script:{code:java}node('linux') {timestamps {stage('all') { echo 'Hello World' sh label: 'ls', script: 'ls -lgGR /bin /lib /lib64 /opt /usr'}}}{code}Unfortunately, I could not reproduce the issue.Could you try to runs the script on an OSX agent to verify whether it is related to cmakebuilder or to pipeline?
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56784) Store console output in S3
Title: Message Title JD Friedrikson created an issue Jenkins / JENKINS-56784 Store console output in S3 Issue Type: Improvement Assignee: Unassigned Components: artifact-manager-s3-plugin Created: 2019-03-27 19:39 Priority: Minor Reporter: JD Friedrikson Currently, it seems that only artifacts are being stored in S3 while the console output is being stored on disk. Given that output for some builds can be quite sizable, I think it would be useful to have the option of also storing console output in S3. Add Comment
[JIRA] (JENKINS-20694) When attempting to connect to destination we receive: jenkins.plugins.publish_over.BapPublisherException: Failed to connect session for config [BETA Unix Server]. Message [Auth
Title: Message Title Alex Earl commented on JENKINS-20694 Re: When attempting to connect to destination we receive: jenkins.plugins.publish_over.BapPublisherException: Failed to connect session for config [BETA Unix Server]. Message [Auth cancel] Please provide details on BigFix. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56783) Use filter and set the common attributes in the events
Title: Message Title David Olorundare edited a comment on JENKINS-56783 Re: Use filter and set the common attributes in the events [~gayathriirajendar] This is *not* a bug. Please fill out a proper description for this and don't just leave it empty. You can take a look at other Jenkins issues in Jira related to the project , to see the correct formatting for newly created issues.Item tasks on the Board in the `To Do` pile do not get assigned to someone until they are moved to the `In Progress` list. So either move this task into the `In Progress` pile if you are working on it otherwise set the Assignee to `Unassigned` Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56783) Use filter and set the common attributes in the events
Title: Message Title David Olorundare edited a comment on JENKINS-56783 Re: Use filter and set the common attributes in the events [~gayathriirajendar] This is *not* a bug. Fill Please fill out a proper description for this and don't just leave it empty. You can take a look at other Jenkins issues in Jira, to see the correct formatting for newly created issues.Item tasks on the Board in the `To Do` pile do not get assigned to someone until they are moved to the `In Progress` list. So either move this task into the `In Progress` pile if you are working on it otherwise set the Assignee to `Unassigned` Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-20694) When attempting to connect to destination we receive: jenkins.plugins.publish_over.BapPublisherException: Failed to connect session for config [BETA Unix Server]. Message [Auth
Title: Message Title k m edited a comment on JENKINS-20694 Re: When attempting to connect to destination we receive: jenkins.plugins.publish_over.BapPublisherException: Failed to connect session for config [BETA Unix Server]. Message [Auth cancel] I'm using the 1.20.1 version of plugin which was working fine so far. There is no change in the plugin version. But there is a change on the remote host to which I'm doing ssh using this plugin. That remote host got patched with BigFix by our linux engineering team. After the patch (BigFix- you can google it) upgrade on that remote linux box, the plugin is giving above error. When i do manually ssh to that remote box (from command line), it is working. But with plugin the connection test itself is failing. There is another jenkins plugin for ssh, it is called "SSH" (can be found at url [https://wiki.jenkins.io/display/JENKINS/SSH+plugin)] this plugin is working fine. I like "Publishing Over SSH" plugin over ssh "SSH" , because I can transfer files as well. hope this gives you enough details. | | Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-20694) When attempting to connect to destination we receive: jenkins.plugins.publish_over.BapPublisherException: Failed to connect session for config [BETA Unix Server]. Message [Auth
Title: Message Title k m edited a comment on JENKINS-20694 Re: When attempting to connect to destination we receive: jenkins.plugins.publish_over.BapPublisherException: Failed to connect session for config [BETA Unix Server]. Message [Auth cancel] I'm using the 1.20.1 version of plugin which was working fine so far. There is no change in the plugin version. But there is a change on the remote host to which I'm doing ssh using this plugin. That remote host got patched with BigFix by our linux engineering team. after that After the patch (BigFix- you can google it) upgrade on that remote linux box, the plugin is giving above error. When i do manually ssh to that remote box (from command line), it is working. But with plugin the connection test itself is failing. There is another jenkins plugin for ssh, it is called "SSH" (can be found at url [https://wiki.jenkins.io/display/JENKINS/SSH+plugin)] this plugin is working fine. I like "Publishing Over SSH" plugin over ssh, because I can transfer files as well. hope this gives you enough details. | | Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56752) Ability to embed charts into other pages
Title: Message Title Ulli Hafner assigned an issue to Unassigned All charts are now rendered on the client side. Currently there is no rendering engine on the server available. I don't know if it is feasible to use the data model of the client chart for such a feature. Jenkins / JENKINS-56752 Ability to embed charts into other pages Change By: Ulli Hafner Labels: help-wanted Assignee: Ulli Hafner Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-20694) When attempting to connect to destination we receive: jenkins.plugins.publish_over.BapPublisherException: Failed to connect session for config [BETA Unix Server]. Message [Auth
Title: Message Title k m edited a comment on JENKINS-20694 Re: When attempting to connect to destination we receive: jenkins.plugins.publish_over.BapPublisherException: Failed to connect session for config [BETA Unix Server]. Message [Auth cancel] I'm using the 1.20.1 version of plugin which was working fine so far. there There is not no change in the plugin version . But there is a change on the remote host to which I'm doing ssh using this plugin. That remote host got patched with BigFix by our linux engineering team. after that patch upgrade on that remote linux box, the plugin is giving above error. When i do manually ssh to that remote box (from command line), it is working. But with plugin the connection test itself is failing. There is another jenkins plugin for ssh, it is called "SSH" (can be found at url [https://wiki.jenkins.io/display/JENKINS/SSH+plugin)] this plugin is working fine. I like "Publishing Over SSH" plugin over ssh, because I can transfer files as well. hope this gives you enough details. | | Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-20694) When attempting to connect to destination we receive: jenkins.plugins.publish_over.BapPublisherException: Failed to connect session for config [BETA Unix Server]. Message [Auth
Title: Message Title k m commented on JENKINS-20694 Re: When attempting to connect to destination we receive: jenkins.plugins.publish_over.BapPublisherException: Failed to connect session for config [BETA Unix Server]. Message [Auth cancel] I'm using the 1.20.1 version of plugin which was working fine so far. there is not change in the plugin. But there is a change on the remote host to which I'm doing ssh using this plugin. That remote host got patched with BigFix by our linux engineering team. after that patch upgrade on that remote linux box, the plugin is giving above error. When i do manually ssh to that remote box (from command line), it is working. But with plugin the connection test itself is failing. There is another jenkins plugin for ssh, it is called "SSH" (can be found at url https://wiki.jenkins.io/display/JENKINS/SSH+plugin) this plugin is working fine. I like "Publishing Over SSH" plugin over ssh, because I can transfer files as well. hope this gives you enough details. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56783) Use filter and set the common attributes in the events
Title: Message Title David Olorundare edited a comment on JENKINS-56783 Re: Use filter and set the common attributes in the events [~gayathriirajendar] This is *not* a bug. Fill out a proper description for this and don't just leave it empty. You can take alook a look at other Jenkins issues in Jira , to see the correct formatting for newly created issues. Items Item tasks on the Board in the `To Do` pile do not get assigned to someone until they are moved to the `In Progress` list. So either move this Task task into the `In Progress` pile if you are working on it otherwise set the Assignee to `Unassigned` Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56783) Use filter and set the common attributes in the events
Title: Message Title David Olorundare edited a comment on JENKINS-56783 Re: Use filter and set the common attributes in the events [~gayathriirajendar] This is *not* a bug. Fill out a proper description for this and don't just leave it empty. You can take alook at other Jenkins issues in Jira to see the correct formatting for newly created issues. Items in the `To Do` pile do not get assigned to someone until they are moved to the `In Progress` list. So either move this Task into the `In Progress` pile if you are working on it otherwise set the person it is assigned to as `Unassigned` Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56783) Use filter and set the common attributes in the events
Title: Message Title David Olorundare edited a comment on JENKINS-56783 Re: Use filter and set the common attributes in the events [~gayathriirajendar] This is *not* a bug. Fill out a proper description for this and don't just leave it empty. You can take alook at other Jenkins issues in Jira to see the correct formatting for newly created issues.Items in the `To Do` pile do not get assigned to someone until they are moved to the `In Progress` list. So either move this Task into the `In Progress` pile if you are working on it otherwise set the person it is assigned Assignee to as `Unassigned` Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56779) yamllint never finds issues
Title: Message Title
Ulli Hafner edited a comment on JENKINS-56779
Re: yamllint never finds issues
Are there options available? The support format looks different:{noformat}file.yml:6:2: [warning] missing starting space in comment (comments)test/file.yml:57:1: [error] trailing spaces (trailing-spaces)file.yml:60:3: [error] wrong indentation: expected 4 but found 2 (indentation)./molecule-default/create.yml:117:89: [error] syntax error: expected '', but found ''{noformat} Which version of yamllint did you use?
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56779) yamllint never finds issues
Title: Message Title
Ulli Hafner edited a comment on JENKINS-56779
Re: yamllint never finds issues
Are there options available? The support format looks different:{noformat}file.yml:6:2: [warning] missing starting space in comment (comments)test/file.yml:57:1: [error] trailing spaces (trailing-spaces)file.yml:60:3: [error] wrong indentation: expected 4 but found 2 (indentation)./molecule-default/create.yml:117:89: [error] syntax error: expected '', but found ''{ norformat noformat }
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56779) yamllint never finds issues
Title: Message Title
Ulli Hafner commented on JENKINS-56779
Re: yamllint never finds issues
Are there options available? The support format looks different:
file.yml:6:2: [warning] missing starting space in comment (comments) test/file.yml:57:1: [error] trailing spaces (trailing-spaces) file.yml:60:3: [error] wrong indentation: expected 4 but found 2 (indentation) ./molecule-default/create.yml:117:89: [error] syntax error: expected '', but found '' {norformat}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56783) Use filter and set the common attributes in the events
Title: Message Title David Olorundare commented on JENKINS-56783 Re: Use filter and set the common attributes in the events Gayathri Rajendar This is not a bug. Fill out a proper description for this and don't just leave it empty. Items in the `To Do` pile do not get assigned to someone until they are moved to the `In Progress` list. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-20694) When attempting to connect to destination we receive: jenkins.plugins.publish_over.BapPublisherException: Failed to connect session for config [BETA Unix Server]. Message [Auth
Title: Message Title k m edited a comment on JENKINS-20694 Re: When attempting to connect to destination we receive: jenkins.plugins.publish_over.BapPublisherException: Failed to connect session for config [BETA Unix Server]. Message [Auth cancel] The issue was not happening until there was some a *BigFix* change made for the remote hosts. Hope this can give some idea. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56674) In case of execute withDockerContainer inside withDockerCotainer env variables is not masked
Title: Message Title Jesse Glick commented on JENKINS-56674 Re: In case of execute withDockerContainer inside withDockerCotainer env variables is not masked Vladimir Kravets please follow responsible disclosure procedures if you even have reason to suspect a security vulnerability anywhere in Jenkins. In this case I am not convinced there is a legitimate vulnerability anyway. Running a nested copy of withDockerContainer has no plausible meaning and can be disregarded. Some other (non-sh) steps may run Launcher in non-quiet mode, in which case the Decorator could be printing environment variables in plaintext. Generally speaking that is not considered a risk, since anything which binds genuine secrets to the environment (like withCredentials) should also be masking them against accidental disclosure, though we still prefer to use ArgumentListBuilder.addMasked just in case, as DockerClient.run does in this example. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51794) Multiple builds start from the same commit
Title: Message Title Mathew Joseph commented on JENKINS-51794 Re: Multiple builds start from the same commit Hi Leandro, Did you find a solution or workaround for this? Happens to me as well. Triggers of quite a few builds at the same time. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56640) Log audit event for item creation
Title: Message Title Gayathri Rajendar updated JENKINS-56640 Jenkins / JENKINS-56640 Log audit event for item creation Change By: Gayathri Rajendar Status: In Review Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56647) Log audit event for node updates
Title: Message Title Gayathri Rajendar updated JENKINS-56647 Jenkins / JENKINS-56647 Log audit event for node updates Change By: Gayathri Rajendar Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56783) Use filter and set the common attributes in the events
Title: Message Title Gayathri Rajendar assigned an issue to Gayathri Rajendar Jenkins / JENKINS-56783 Use filter and set the common attributes in the events Change By: Gayathri Rajendar Assignee: David Olorundare Gayathri Rajendar Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56783) Use filter and set the common attributes in the events
Title: Message Title Gayathri Rajendar created an issue Jenkins / JENKINS-56783 Use filter and set the common attributes in the events Issue Type: Bug Assignee: David Olorundare Components: audit-log-plugin Created: 2019-03-27 18:31 Priority: Minor Reporter: Gayathri Rajendar Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56647) Log audit event for node updates
Title: Message Title Gayathri Rajendar updated JENKINS-56647 Jenkins / JENKINS-56647 Log audit event for node updates Change By: Gayathri Rajendar Status: In Review Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56640) Log audit event for item creation
Title: Message Title Gayathri Rajendar updated JENKINS-56640 Jenkins / JENKINS-56640 Log audit event for item creation Change By: Gayathri Rajendar Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-20694) When attempting to connect to destination we receive: jenkins.plugins.publish_over.BapPublisherException: Failed to connect session for config [BETA Unix Server]. Message [Auth
Title: Message Title Alex Earl commented on JENKINS-20694 Re: When attempting to connect to destination we receive: jenkins.plugins.publish_over.BapPublisherException: Failed to connect session for config [BETA Unix Server]. Message [Auth cancel] What version of the plugin are you using and what previous version worked? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-20694) When attempting to connect to destination we receive: jenkins.plugins.publish_over.BapPublisherException: Failed to connect session for config [BETA Unix Server]. Message [Auth
Title: Message Title k m commented on JENKINS-20694 Re: When attempting to connect to destination we receive: jenkins.plugins.publish_over.BapPublisherException: Failed to connect session for config [BETA Unix Server]. Message [Auth cancel] The issue was not happening until there was some BigFix made for the remote hosts. Hope this can give some idea. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54910) Could not able to Build Azure Function APP using MSBuild Plugin
Title: Message Title Luba Pyat commented on JENKINS-54910 Re: Could not able to Build Azure Function APP using MSBuild Plugin Any updates on this issue? We have very similar... Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54018) NoClassDefFoundError: Lhudson/tools/JDKInstaller when JDK Tools plugin is uninstalled
Title: Message Title Ian Williams commented on JENKINS-54018 Re: NoClassDefFoundError: Lhudson/tools/JDKInstaller when JDK Tools plugin is uninstalled I was not clear on the difference between implied and optional. I understand the dependencies cannot be fixed retroactively. I guess this is an unfortunate outcome. Before closing this I suppose a mitigating fix would be to have documented in the install_plugins.sh and elsewhere, the list of plugins which where split off that at considered mandatory. The best approach is maybe a reference to a wiki page which contains the list. It would seem this requirement was also merely implied in the LTS Upgrade Notes as I did not read this. can the upgrade guide get a note added as well? A user should not have to dig through JIRA tickets or PRs to figure this out. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54376) needs documentation
Title: Message Title Tomas Salazar updated JENKINS-54376 https://plugins.jenkins.io/nvm-wrapper Jenkins / JENKINS-54376 needs documentation Change By: Tomas Salazar Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53790) Kubernetes plugin shows failing templates to only admins
Title: Message Title Jesse Glick updated JENKINS-53790 Jenkins / JENKINS-53790 Kubernetes plugin shows failing templates to only admins Change By: Jesse Glick Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53790) Kubernetes plugin shows failing templates to only admins
Title: Message Title Jesse Glick started work on JENKINS-53790 Change By: Jesse Glick Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53790) Kubernetes plugin shows failing templates to only admins
Title: Message Title Jesse Glick assigned an issue to Pierson Yieh Jenkins / JENKINS-53790 Kubernetes plugin shows failing templates to only admins Change By: Jesse Glick Assignee: Carlos Sanchez Pierson Yieh Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33185) Visualize parallel steps within a Pipeline Stage
Title: Message Title
Joshua Einstein-Curtis commented on JENKINS-33185
Re: Visualize parallel steps within a Pipeline Stage
I was wondering whatever happened to this? We have an architecture like the pseudo-code below, where the parallel is a stage, but the stages in the parallel aren't broken out. We need to do this to get different nodes within a stage. If there is a better way to do this so the visualization works, we'd love to know, but it is currently an ugly visual representation with only the first stage and the parallel stage, basically.
def jobMap (
some['thing'] = {node (label) {
stage1
stage2
} }
)
node {
def jobs = jobMap()
stage1
stage2 {
parallel jobs
}
}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-20694) When attempting to connect to destination we receive: jenkins.plugins.publish_over.BapPublisherException: Failed to connect session for config [BETA Unix Server]. Message [Auth
Title: Message Title Alex Earl commented on JENKINS-20694 Re: When attempting to connect to destination we receive: jenkins.plugins.publish_over.BapPublisherException: Failed to connect session for config [BETA Unix Server]. Message [Auth cancel] I can't reproduce this issue at all, so I have no way to debug it. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56767) Unexpected exception occurred while performing online-node command
Title: Message Title Chance Davies updated an issue Jenkins / JENKINS-56767 Unexpected exception occurred while performing online-node command Change By: Chance Davies Attachment: java.nio.channels.ClosedChannelException.txt Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56767) Unexpected exception occurred while performing online-node command
Title: Message Title Chance Davies updated an issue Jenkins / JENKINS-56767 Unexpected exception occurred while performing online-node command Change By: Chance Davies Attachment: Unexpected exception occurred while performing online-node command.txt Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56767) Unexpected exception occurred while performing online-node command
Title: Message Title Chance Davies updated an issue Jenkins / JENKINS-56767 Unexpected exception occurred while performing online-node command Change By: Chance Davies Attachment: Job Randomly Aborted.txt Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51183) Create a demo Integration testing flow for Artifact Manager S3
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-51183 Create a demo Integration testing flow for Artifact Manager S3 Change By: Jesse Glick Labels: evergreen incrementals stalled-pr Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56740) Artifacts bigger than 5GB can't be uploaded to S3
Title: Message Title Jesse Glick assigned an issue to Artem V. Navrotskiy Jenkins / JENKINS-56740 Artifacts bigger than 5GB can't be uploaded to S3 Change By: Jesse Glick Assignee: Artem V. Navrotskiy Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56740) Artifacts bigger than 5GB can't be uploaded to S3
Title: Message Title Jesse Glick updated JENKINS-56740 Jenkins / JENKINS-56740 Artifacts bigger than 5GB can't be uploaded to S3 Change By: Jesse Glick Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56740) Artifacts bigger than 5GB can't be uploaded to S3
Title: Message Title Jesse Glick started work on JENKINS-56740 Change By: Jesse Glick Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52888) Add option to use AWS S3 accelerated endpoint
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-52888 Add option to use AWS S3 accelerated endpoint Change By: Jesse Glick Labels: stalled-pr Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52888) Add option to use AWS S3 accelerated endpoint
Title: Message Title Jesse Glick started work on JENKINS-52888 Change By: Jesse Glick Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52888) Add option to use AWS S3 accelerated endpoint
Title: Message Title Jesse Glick assigned an issue to Kostiantyn Luzan Jenkins / JENKINS-52888 Add option to use AWS S3 accelerated endpoint Change By: Jesse Glick Assignee: Kostiantyn Luzan Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52888) Add option to use AWS S3 accelerated endpoint
Title: Message Title Jesse Glick updated JENKINS-52888 Jenkins / JENKINS-52888 Add option to use AWS S3 accelerated endpoint Change By: Jesse Glick Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55994) Demo and Test Automation for showing Jenkinsfile Runner on Java 11
Title: Message Title Evaristo Gutierrez updated JENKINS-55994 Jenkins / JENKINS-55994 Demo and Test Automation for showing Jenkinsfile Runner on Java 11 Change By: Evaristo Gutierrez Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55994) Demo and Test Automation for showing Jenkinsfile Runner on Java 11
Title: Message Title Evaristo Gutierrez commented on JENKINS-55994 Re: Demo and Test Automation for showing Jenkinsfile Runner on Java 11 PR: https://github.com/jenkinsci/jenkinsfile-runner/pull/102 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56780) The TFS plugin is not working correctly with the "exclude regions" feature
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-56780 The TFS plugin is not working correctly with the "exclude regions" feature Change By: Mark Waite When we use TFS for a Git repository and I configure a webhook from the Azure UI using "Perform this action": "Trigger git build" and "Integration level":"Built-in Jenkins API" the hook received trigger the build but it doesn't use any of the additional behaviors defined like the exclude regions.Using polling it works without any issue. I have been reviewed deeply the issue and the hook received on the Jenkins side looks like that one: _Received notification from xx.xxx.xxx.xxx → xx.xx.x.xxx → xx.xxx.xxx.xxx ⇒ https://jenkins-url/git/notifyCommit for uri = https://dev.azure.com/repo/test/_git/test ; sha1 = 71c8xxx5xxx9x54fxx96cxb53x78 ; branches = [master]_If the git plugin receives a sha1 parameter it just lunches launches the build related to that SHA1 without checking anything, so probably the error is on the webhook side that is sending an incorrect hook , though the git plugin should reasonably not be accepting a SHA1 argument without applying the usual checks to decide if that SHA1 should be built. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To
[JIRA] (JENKINS-56780) The TFS plugin is not working correctly with the "exclude regions" feature
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-56780 The TFS plugin is not working correctly with the "exclude regions" feature Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-20694) When attempting to connect to destination we receive: jenkins.plugins.publish_over.BapPublisherException: Failed to connect session for config [BETA Unix Server]. Message [Auth
Title: Message Title k m reopened an issue Please reopen the issue as this still exists. Jenkins / JENKINS-20694 When attempting to connect to destination we receive: jenkins.plugins.publish_over.BapPublisherException: Failed to connect session for config [BETA Unix Server]. Message [Auth cancel] Change By: k m Resolution: Cannot Reproduce Status: Closed Reopened Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-20694) When attempting to connect to destination we receive: jenkins.plugins.publish_over.BapPublisherException: Failed to connect session for config [BETA Unix Server]. Message [Auth
Title: Message Title k m commented on JENKINS-20694 Re: When attempting to connect to destination we receive: jenkins.plugins.publish_over.BapPublisherException: Failed to connect session for config [BETA Unix Server]. Message [Auth cancel] The issue still exists. Can you please check? The Jenkins SSH plugin is working fine (https://wiki.jenkins.io/display/JENKINS/SSH+plugin). This is an issue while using plugin "Publish Over SSH" (https://wiki.jenkins.io/display/JENKINS/Publish+Over+SSH+Plugin) while using user id and password for authentication but authentication via key is working fine. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-20694) When attempting to connect to destination we receive: jenkins.plugins.publish_over.BapPublisherException: Failed to connect session for config [BETA Unix Server]. Message [Auth
Title: Message Title k m updated an issue Jenkins / JENKINS-20694 When attempting to connect to destination we receive: jenkins.plugins.publish_over.BapPublisherException: Failed to connect session for config [BETA Unix Server]. Message [Auth cancel] Change By: k m Attachment: Screen Shot 2019-03-27 at 12.08.42 PM.jpg Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56782) EBS encryption support
Title: Message Title JD Friedrikson created an issue Jenkins / JENKINS-56782 EBS encryption support Issue Type: Improvement Assignee: FABRIZIO MANFREDI Components: ec2-plugin Created: 2019-03-27 15:48 Priority: Minor Reporter: JD Friedrikson Cloud templates for the EC2 should include a field to enable disk encryption for EBS volumes. Currently, it seems to be unencrypted without any option to specify otherwise. For builds that include sensitive information, this is a must. Add Comment This
[JIRA] (JENKINS-56781) Option to use a variable for 'container' reference
Title: Message Title
Alex Dixon created an issue
Jenkins / JENKINS-56781
Option to use a variable for 'container' reference
Issue Type:
Improvement
Assignee:
Carlos Sanchez
Components:
kubernetes-plugin
Created:
2019-03-27 15:46
Labels:
user-experience
Priority:
Minor
Reporter:
Alex Dixon
For example, I will define all my containers in yaml and then I would like to make the container reference a variable. stage("Build") { steps { script { container (${imageName}) { This will make it easier to template JenkinsFiles for multiple builds that require a separate image.
Add Comment
[JIRA] (JENKINS-56780) The TFS plugin is not working correctly with the "exclude regions" feature
Title: Message Title Javier Raez created an issue Jenkins / JENKINS-56780 The TFS plugin is not working correctly with the "exclude regions" feature Issue Type: Improvement Assignee: Mark Waite Components: git-plugin, tfs-plugin Created: 2019-03-27 15:28 Priority: Minor Reporter: Javier Raez When we use TFS for a Git repository and I configure a webhook from the Azure UI using "Perform this action": "Trigger git build" and "Integration level":"Built-in Jenkins API" the hook received trigger the build but it doesn't use any of the additional behaviors defined like the exclude regions. Using polling it works without any issue. I have been reviewed deeply the issue and the hook received on the Jenkins side looks like that one: Received notification from xx.xxx.xxx.xxx → xx.xx.x.xxx → xx.xxx.xxx.xxx ⇒ https://jenkins-url/git/notifyCommit for uri = https://dev.azure.com/repo/test/_git/test ; sha1 = 71c8xxx5xxx9x54fxx96cxb53x78 ; branches = [master] If the git plugin receives a sha1 parameter it just lunches the build related to that SHA1 without checking anything, so probably the error is on the webhook side that is sending an incorrect hook Add Comment
[JIRA] (JENKINS-53379) Source code not shown when using folders plugin
Title: Message Title Torben Stößel edited a comment on JENKINS-53379 Re: Source code not shown when using folders plugin I can report similar behavior. We have a multi-branch Bitbucket source project and C++ code. We generate Cobertura report with gcovr. Used environment: Ubuntu 16.04, Jenkins core 2.150.2, Cobertura 1.12.1 and also tried 1.13. If that matters, Folder Plugin 6.7.I know that it worked some time ago, I did an update of jenkins core and all plugins and to be honest, I cannot undo this to figure out when the problem shows up. The strange is that source code of master branch *is properly* shown. Source code of all other branches *is not* shown. This is also why I think that the overall configuration is correct. EDIT: I have to withdraw my argument, that it works properly on master branch. After a new build of the master branch, it did not work either. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56731) Credentials password details can show in output with creds and mask plugins
Title: Message Title Daniel Beck closed an issue as Fixed Masking attempts to prevent accidental disclosure of credentials. It's trivial to bypass and always will be, necessarily. See https://jenkins.io/blog/2019/02/21/credentials-masking/ This case however is simply a lack of proper escaping of user input in a Groovy string that gets interpreted as a shell script. The ampersand character is a shell metacharacter and gets interpreted as such. Use single quotes, see the Pipeline docs. Jenkins / JENKINS-56731 Credentials password details can show in output with creds and mask plugins Change By: Daniel Beck Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more
[JIRA] (JENKINS-56731) Credentials password details can show in output with creds and mask plugins
Title: Message Title Daniel Beck closed an issue as Not A Defect Jenkins / JENKINS-56731 Credentials password details can show in output with creds and mask plugins Change By: Daniel Beck Status: Reopened Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56731) Credentials password details can show in output with creds and mask plugins
Title: Message Title Daniel Beck reopened an issue Jenkins / JENKINS-56731 Credentials password details can show in output with creds and mask plugins Change By: Daniel Beck Resolution: Fixed Status: Closed Reopened Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56779) yamllint never finds issues
Title: Message Title
g hs1 created an issue
Jenkins / JENKINS-56779
yamllint never finds issues
Issue Type:
Bug
Assignee:
Ulli Hafner
Components:
warnings-ng-plugin
Created:
2019-03-27 14:50
Environment:
Various linux and Windows servers Jenkins 2.160+
Priority:
Major
Reporter:
g hs1
I have managed to get ansible-lint to report failures but the yamllint parser never works. It doesn't matter if I write to a log amd parse that, parse the console, separate scanning and publishng. The result is always no issues found.
[Pipeline] { (Run yamllint)
[Pipeline] sh
14:41:07 + yamllint ./
14:41:08 ./windows-utilities.yml
14:41:086:1 errortoo many blank lines (2 > 1) (empty-lines)
14:41:087:1 warning comment not indented like content (comments-indentation)
14:41:087:2 warning missing starting space in comment (comments)
14:41:089:1 errortoo many blank lines (2 > 1) (empty-lines)
14:41:0811:22 errorno new line character at the end of file (new-line-at-end-of-file)
14:41:08
[Pipeline] echo
14:41:08 hudson.AbortException: script returned exit code 1
[Pipeline] recordIssues
14:41:08 Skipping issues blame since Git is the only supported SCM up to now.
14:41:08 [YamlLint] Sleeping for 5 seconds due to JENKINS-32191...
14:41:13 [YamlLint] Parsing console log (workspace: '/var/lib/jenkins/workspace/CC3')
14:41:13 [YamlLint] Attaching ResultAction with ID 'yamllint' to run 'CC3 #21'.
14:41:13 [YamlLint] Using reference build 'CC3 #20' to compute new, fixed, and outstanding issues
14:41:13 [YamlLint] Issues delta (vs. reference
[JIRA] (JENKINS-46094) "Checkout over SSH" fails the build since it still uses HTTPS urls
Title: Message Title Liam Newman commented on JENKINS-46094 Re: "Checkout over SSH" fails the build since it still uses HTTPS urls Bitbucket has been published. I will publish github today. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56779) yamllint never finds issues
Title: Message Title
g hs1 created an issue
Jenkins / JENKINS-56779
yamllint never finds issues
Issue Type:
Bug
Assignee:
Ulli Hafner
Components:
warnings-ng-plugin
Created:
2019-03-27 14:50
Environment:
Various linux and Windows servers Jenkins 2.160+
Priority:
Major
Reporter:
g hs1
I have managed to get ansible-lint to report failures but the yamllint parser never works. It doesn't matter if I write to a log amd parse that, parse the console, separate scanning and publishng. The result is always no issues found.
[Pipeline] { (Run yamllint)
[Pipeline] sh
14:41:07 + yamllint ./
14:41:08 ./windows-utilities.yml
14:41:086:1 errortoo many blank lines (2 > 1) (empty-lines)
14:41:087:1 warning comment not indented like content (comments-indentation)
14:41:087:2 warning missing starting space in comment (comments)
14:41:089:1 errortoo many blank lines (2 > 1) (empty-lines)
14:41:0811:22 errorno new line character at the end of file (new-line-at-end-of-file)
14:41:08
[Pipeline] echo
14:41:08 hudson.AbortException: script returned exit code 1
[Pipeline] recordIssues
14:41:08 Skipping issues blame since Git is the only supported SCM up to now.
14:41:08 [YamlLint] Sleeping for 5 seconds due to JENKINS-32191...
14:41:13 [YamlLint] Parsing console log (workspace: '/var/lib/jenkins/workspace/CC3')
14:41:13 [YamlLint] Attaching ResultAction with ID 'yamllint' to run 'CC3 #21'.
14:41:13 [YamlLint] Using reference build 'CC3 #20' to compute new, fixed, and outstanding issues
14:41:13 [YamlLint] Issues delta (vs. reference
[JIRA] (JENKINS-46094) "Checkout over SSH" fails the build since it still uses HTTPS urls
Title: Message Title Liam Newman assigned an issue to Liam Newman Jenkins / JENKINS-46094 "Checkout over SSH" fails the build since it still uses HTTPS urls Change By: Liam Newman Assignee: Liam Newman Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46094) "Checkout over SSH" fails the build since it still uses HTTPS urls
Title: Message Title Liam Newman updated JENKINS-46094 Jenkins / JENKINS-46094 "Checkout over SSH" fails the build since it still uses HTTPS urls Change By: Liam Newman Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46094) "Checkout over SSH" fails the build since it still uses HTTPS urls
Title: Message Title Liam Newman started work on JENKINS-46094 Change By: Liam Newman Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56750) Micro Focus Application Automation Tools - Build log incorrect for multiple test instances of the same test.
Title: Message Title Daniel Gront updated an issue Jenkins / JENKINS-56750 Micro Focus Application Automation Tools - Build log incorrect for multiple test instances of the same test. Change By: Daniel Gront Labels: Center Quality ALM Results Test Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56750) Micro Focus Application Automation Tools - Build log incorrect for multiple test instances of the same test.
Title: Message Title Daniel Gront assigned an issue to Roy Lu Jenkins / JENKINS-56750 Micro Focus Application Automation Tools - Build log incorrect for multiple test instances of the same test. Change By: Daniel Gront Assignee: Carles Capdevila Roy Lu Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
