[JIRA] (JENKINS-44601) Provide an option to create preemptible GCloud VM instances
Title: Message Title Fritz Elfert updated JENKINS-44601 Committed to master. Please test (I don't have a GCP account anymore) Will be released in 2.16. Sorry it took so long. Jenkins / JENKINS-44601 Provide an option to create preemptible GCloud VM instances Change By: Fritz Elfert Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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
[JIRA] (JENKINS-60469) Doxygen parser not detecting error
Title: Message Title Ulli Hafner assigned an issue to Unassigned Jenkins / JENKINS-60469 Doxygen parser not detecting error Change By: Ulli Hafner Component/s: analysis-model Component/s: warnings-ng-plugin Labels: help-wanted newbie-friendly Assignee: Ulli Hafner Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://grou
[JIRA] (JENKINS-47301) JClouds aws-ec2 always tries to use default subnet
Title: Message Title Fritz Elfert updated JENKINS-47301 Committed to master. Please test (I don't have an AWS account anymore) Will be released in 2.16. Sorry it took so long. Jenkins / JENKINS-47301 JClouds aws-ec2 always tries to use default subnet Change By: Fritz Elfert Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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-44601) Provide an option to create preemptible GCloud VM instances
Title: Message Title Fritz Elfert edited a comment on JENKINS-44601 Re: Provide an option to create preemptible GCloud VM instances Committed to master (added a help text as well) . Please test (I don't have a GCP account anymore)Will be released in 2.16. Sorry it took so long. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.182456.1496305444000.7493.1576321800220%40Atlassian.JIRA.
[JIRA] (JENKINS-60440) Invalid git username/password on Jenkins agent when using Vault Username-Password Credential
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-60440 Invalid git username/password on Jenkins agent when using Vault Username-Password Credential Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203515.1576064724000.7499.1576324860209%40Atlassian.JIRA.
[JIRA] (JENKINS-60440) Invalid git username/password on Jenkins agent when using Vault Username-Password Credential
Title: Message Title Mark Waite commented on JENKINS-60440 Re: Invalid git username/password on Jenkins agent when using Vault Username-Password Credential Submitter notes that an @ sign embedded in the username will cause authentication failures in the git client plugin. Also an issue for the google code repositories since their user names include an @ sign as well. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203515.1576064724000.7501.1576325280122%40Atlassian.JIRA.
[JIRA] (JENKINS-60440) Invalid git username/password on Jenkins agent when using Vault Username-Password Credential
Title: Message Title Mark Waite edited a comment on JENKINS-60440 Re: Invalid git username/password on Jenkins agent when using Vault Username-Password Credential Submitter notes that an \@ sign embedded in the username will cause authentication failures in the git client plugin. Also an issue for the google code repositories since their user names include an \@ sign as well. I assume the use of an embedded \@ character in the username is used on Bitbucket Server and Bitbucket Data Center. I use markewaite as my Bitbucket Cloud username. Bitbucket Cloud knows my google e-mail address and has connected my google e-mail address to my Bitbucket Cloud account.Can you define a username in Bitbucket server that does not include the \@ character in the username? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203515.1576064724000.7503.1576325760133%40Atlassian.JIRA.
[JIRA] (JENKINS-60440) Invalid git username/password on Jenkins agent when using Vault Username-Password Credential
Title: Message Title Mark Waite edited a comment on JENKINS-60440 Re: Invalid git username/password on Jenkins agent when using Vault Username-Password Credential Submitter notes that an \@ sign embedded in the username will cause authentication failures in the git client plugin. Also an issue for the google code repositories since their user names include an \@ sign as well.I assume the use of an embedded \@ character in the username is used on Bitbucket Server and Bitbucket Data Center. I use markewaite as my [ Bitbucket Cloud username |https://bitbucket . org/%7Bfeeb1516-e0f7-4759-89a0-1d3fe983b1f8%7D/]. Bitbucket Cloud knows my google e-mail address and has connected my google e-mail address to my Bitbucket Cloud account.Can you define a username in Bitbucket server that does not include the \@ character in the username? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203515.1576064724000.7505.1576325820120%40Atlassian.JIRA.
[JIRA] (JENKINS-60440) Invalid git username/password on Jenkins agent when using Vault Username-Password Credential
Title: Message Title Mark Waite edited a comment on JENKINS-60440 Re: Invalid git username/password on Jenkins agent when using Vault Username-Password Credential Submitter notes that an \@ sign embedded in the username will cause authentication failures in the git client plugin. Also an issue for the google code repositories since their user names include an \@ sign as well.I assume the use of an embedded \@ character in the username is used on Bitbucket Server and Bitbucket Data Center. I use markewaite as my [Bitbucket Cloud username|https://bitbucket.org/%7Bfeeb1516-e0f7-4759-89a0-1d3fe983b1f8%7D/]. Bitbucket Cloud knows my google e-mail address and has connected my google e-mail address to my Bitbucket Cloud account.Can you define a username in Bitbucket server that does not include the \@ character in the username? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203515.1576064724000.7507.1576325880139%40Atlassian.JIRA.
[JIRA] (JENKINS-60440) Invalid git username/password on Jenkins agent when using Vault Username-Password Credential
Title: Message Title Mark Waite edited a comment on JENKINS-60440 Re: Invalid git username/password on Jenkins agent when using Vault Username-Password Credential Submitter notes that an \@ sign embedded in the username will cause authentication failures in the git client plugin. Also an issue for the google code repositories since their user names include an \@ sign as well.I was not aware of Bitbucket Cloud supporting a username which includes an \@ character. My Bitbucket Cloud account does not contain an embedded \@ character.I assume the use of an embedded \@ character in the username is used on Bitbucket Server and Bitbucket Data Center. I use markewaite as my [Bitbucket Cloud username|https://bitbucket.org/%7Bfeeb1516-e0f7-4759-89a0-1d3fe983b1f8%7D/]. Bitbucket Cloud knows my google e-mail address and has connected my google e-mail address to my Bitbucket Cloud account.Can you define a username in Bitbucket server that does not include the \@ character in the username? Are you able to define an app password in Bitbucket Cloud, store that app password in Hashicorp Vault, and use that app password as part of a Vault username / password credential? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203515.1576064724000.7509.1576326120128%40Atlassian.JIRA.
[JIRA] (JENKINS-60440) Invalid git username/password on Jenkins agent when using Vault Username-Password Credential with '@' in username
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-60440 Invalid git username/password on Jenkins agent when using Vault Username-Password Credential with '@' in username Change By: Mark Waite Summary: Invalid git username/password on Jenkins agent when using Vault Username-Password Credential with '@' in username Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203515.1576064724000.7511.1576326180126%40Atlassian.JIRA.
[JIRA] (JENKINS-55524) Triggers on wrong branch when pushing multiple merges
Title: Message Title Mark Waite commented on JENKINS-55524 Re: Triggers on wrong branch when pushing multiple merges Aaron Jensen recommends using --points-at instead of --contains. I think that seems like a reasonable idea though it will require special handling for the cases where the command line git version is 2.6.0 or older (CentOS 6, CentOS 7, Red Hat Enterprise Linux 6, Red Hat Enterprise Linux 7, and likely several others). Thankfully, Ubuntu 16 and Debian 9 both include a command line git version that supports the --points-at argument. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196657.1547153222000.7513.1576327320287%40Atlassian.JIRA.
[JIRA] (JENKINS-60477) Jenkins job is over running while creating jar files
Title: Message Title Pierre Beitz commented on JENKINS-60477 Re: Jenkins job is over running while creating jar files Divya Ganesan , this doesn't look like a bug but a configuration issue. Without more details on the job and the configuration it's hard to give a definite answer, but the error most probably means the heap size allocated to the agent running the build is not enough. You should start looking how much you need from outside Jenkins and adjust the heap of the node running the build accordindly. Note that you can set the Heap Size with `-Xmx`, not `-Xx`. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203560.1576254956000.7520.1576329180182%40Atlassian.JIRA.
[JIRA] (JENKINS-59481) Automatically label Fedora Linux agents
Title: Message Title Mark Waite closed an issue as Fixed Jenkins / JENKINS-59481 Automatically label Fedora Linux agents Change By: Mark Waite Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202096.1569240781000.7522.1576336500220%40Atlassian.JIRA.
[JIRA] (JENKINS-59481) Automatically label Fedora Linux agents
Title: Message Title Mark Waite updated JENKINS-59481 Fixed in platform labeler plugin release 5.2 and later Jenkins / JENKINS-59481 Automatically label Fedora Linux agents Change By: Mark Waite Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202096.1569240781000.7521.1576336500153%40Atlassian.JIRA.
[JIRA] (JENKINS-60440) Invalid git username/password on Jenkins agent when using Vault Username-Password Credential with '@' in username
Title: Message Title Gordon Li commented on JENKINS-60440 Re: Invalid git username/password on Jenkins agent when using Vault Username-Password Credential with '@' in username Bitbucket.org no longer allows logging in with a username - they only allow email address or Google/Microsoft logins. I don't think @ character is the problem because the Git plugin works fine if my Bitbucket credentials are stored in Jenkins as "Username with password". Also note that it's only the agent server that fails to use a Vault username/password to checkout a Git repository. The master server is correctly setting the Git credentials and checking out the retrieve the pipeline's jenkinsfile. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203515.1576064724000.7534.1576342860215%40Atlassian.JIRA.
[JIRA] (JENKINS-60440) Invalid git username/password on Jenkins agent when using Vault Username-Password Credential with '@' in username
Title: Message Title Mark Waite edited a comment on JENKINS-60440 Re: Invalid git username/password on Jenkins agent when using Vault Username-Password Credential with '@' in username Submitter notes that an \@ sign embedded in the username will cause authentication failures in the git client plugin. Also an issue for the google code repositories since their user names include an \@ sign as well.I was not aware of Bitbucket Cloud supporting a username which includes an \@ character. My Bitbucket Cloud account username (used to perform the clone) does not contain an embedded \@ character.I assume the use of an embedded \@ character in the username is used on Bitbucket Server and Bitbucket Data Center. I use markewaite as my [Bitbucket Cloud username|https://bitbucket.org/%7Bfeeb1516-e0f7-4759-89a0-1d3fe983b1f8%7D/]. Bitbucket Cloud knows my google e-mail address and has connected my google e-mail address to my Bitbucket Cloud account.Can you define a username in Bitbucket server that does not include the \@ character in the username?Are you able to define an app password in Bitbucket Cloud, store that app password in Hashicorp Vault, and use that app password as part of a Vault username / password credential? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203515.1576064724000.7536.15
[JIRA] (JENKINS-60440) Invalid git username/password on Jenkins agent when using Vault Username-Password Credential with '@' in username
Title: Message Title Mark Waite commented on JENKINS-60440 Re: Invalid git username/password on Jenkins agent when using Vault Username-Password Credential with '@' in username I agree that they don't allow login with a simple username that is not an e-mail address. As far as I can tell, they do seem to allow clone with a simple username even when I performed the login with my e-mail address. My question was attempting to find an alternative that will allow you to operate in your environment without requiring a change from the git client plugin. I don't think that there are major differences between the use of the username / password credential on the master and the use of the username / password credential on the agent. However, there must be enough of a difference to be creating the issue you're seeing. If the failing pipeline checkout operation inside the Jenkinsfile is intentionally executed on the master, does it fail in the same way, or does it succeed? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203515.1576064724000.7538.1576344720106%40Atlassian.JIRA.
[JIRA] (JENKINS-60440) Invalid git username/password on Jenkins agent when using Vault Username-Password Credential with '@' in username
Title: Message Title Mark Waite edited a comment on JENKINS-60440 Re: Invalid git username/password on Jenkins agent when using Vault Username-Password Credential with '@' in username I agree that they don't allow login with a simple username that is not an e-mail address. As far as I can tell, they do seem to allow clone with a simple username even when I performed the login with my e-mail address. My question was attempting to find an alternative that will allow you to operate in your environment without requiring a change from the git client plugin.I don't think that there are major differences between the use of the username / password credential on the master and the use of the username / password credential on the agent. However, there must be enough of a difference to be creating the issue you're seeing. If the failing pipeline checkout operation inside the Jenkinsfile is intentionally executed on the master, does it fail in the same way, or does it succeed? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203515.1576064724000.7540.1576344780125%40Atlassian.JIRA.
[JIRA] (JENKINS-60440) Invalid git username/password on Jenkins agent when using Vault Username-Password Credential with '@' in username
Title: Message Title
Gordon Li commented on JENKINS-60440
Re: Invalid git username/password on Jenkins agent when using Vault Username-Password Credential with '@' in username
The pipeline from SCM job checks out the repo on the master first in order to get the jenkinsfile, then the agent checks out the repo again in order to execute the jenkinsfile. The master is always about to check out while the slave is unable to check out using Vault username/password. On further investigation, I suspect that on the agent, GIT_ASKPASS doesn't get configured correctly when using Vault. If I use a pipeline script defined in the job rather than from SCM, I can set my Git credentials to environment variables GITUSER and GITPASS and execute the following steps to manually configure GIT_ASKPASS before checking out a repository.
sh "git config credential.helper '!f() { sleep 1; echo \"username=${GITUSER}\"; echo \"password=${GITPASS}\"; }; f'"
git url: 'https://bitbucket.org//.git'
This runs successfully on a Linux agent. I haven't figured out how to replicate the git config credential.helper function on Windows so my Windows workaround instead is
git url: "https://${env.GITUSER}:${env.GITPASS}@bitbucket.org//.git"
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-21311) Queue item cancellation via REST api works but returns a 404
Title: Message Title Pierre Beitz started work on JENKINS-21311 Change By: Pierre Beitz Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.152875.1389282741000.7563.1576358522985%40Atlassian.JIRA.
[JIRA] (JENKINS-21311) Queue item cancellation via REST api works but returns a 404
Title: Message Title Pierre Beitz updated JENKINS-21311 Jenkins / JENKINS-21311 Queue item cancellation via REST api works but returns a 404 Change By: Pierre Beitz Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.152875.1389282741000.7573.1576358523117%40Atlassian.JIRA.
[JIRA] (JENKINS-21311) Queue item cancellation via REST api works but returns a 404
Title: Message Title Pierre Beitz assigned an issue to Pierre Beitz Jenkins / JENKINS-21311 Queue item cancellation via REST api works but returns a 404 Change By: Pierre Beitz Assignee: Pierre Beitz Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.152875.1389282741000.7553.1576358522847%40Atlassian.JIRA.
[JIRA] (JENKINS-27975) Audit trail should log query string as well
Title: Message Title Pierre Beitz assigned an issue to Pierre Beitz Jenkins / JENKINS-27975 Audit trail should log query string as well Change By: Pierre Beitz Assignee: Pierre Beitz Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.162172.1429183811000.7605.1576358523605%40Atlassian.JIRA.
[JIRA] (JENKINS-27975) Audit trail should log query string as well
Title: Message Title Pierre Beitz started work on JENKINS-27975 Change By: Pierre Beitz Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.162172.1429183811000.7607.1576358580369%40Atlassian.JIRA.
[JIRA] (JENKINS-27975) Audit trail should log query string as well
Title: Message Title Pierre Beitz updated JENKINS-27975 Jenkins / JENKINS-27975 Audit trail should log query string as well Change By: Pierre Beitz Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.162172.1429183811000.7609.1576358580395%40Atlassian.JIRA.
[JIRA] (JENKINS-21311) Queue item cancellation via REST api works but returns a 404
Title: Message Title Pierre Beitz stopped work on JENKINS-21311 Change By: Pierre Beitz Status: In Progress Open Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.152875.1389282741000.7593.1576358523436%40Atlassian.JIRA.
[JIRA] (JENKINS-21311) Queue item cancellation via REST api works but returns a 404
Title: Message Title Pierre Beitz updated JENKINS-21311 Jenkins / JENKINS-21311 Queue item cancellation via REST api works but returns a 404 Change By: Pierre Beitz Status: In Review Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.152875.1389282741000.7583.1576358523250%40Atlassian.JIRA.
[JIRA] (JENKINS-21311) Queue item cancellation via REST api works but returns a 404
Title: Message Title Pierre Beitz assigned an issue to Unassigned Jenkins / JENKINS-21311 Queue item cancellation via REST api works but returns a 404 Change By: Pierre Beitz Assignee: Pierre Beitz Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.152875.1389282741000.7595.1576358523455%40Atlassian.JIRA.
[JIRA] (JENKINS-60483) jenkins role pattern regex not working , all projects are displayed
Title: Message Title Kiran Singh Sathyanarayan created an issue Jenkins / JENKINS-60483 jenkins role pattern regex not working , all projects are displayed Issue Type: Bug Assignee: Oleg Nenashev Attachments: Unable_to_Show_jobs-1.png, Unable_to_Show_jobs-2.png, Unable_to_Show_jobs-3.png Components: role-strategy-plugin Created: 2019-12-14 22:09 Environment: windows 10 Priority: Critical Reporter: Kiran Singh Sathyanarayan i wanted to display projects which starts only with helo for particular user but its displaying all projects , can you help me out with regex pattrens tried with helo-.* helo(.*) after applying regex patterns all projects are displayed , find the attached screen shots one by one tried in all possible ways to resolve issue unable to show projects starts with helo Regards, Kiran devopsksath...@gmail.com +91-9886370303
[JIRA] (JENKINS-60483) jenkins role pattern regex not working , all projects are displayed
Title: Message Title Kiran Singh Sathyanarayan commented on JENKINS-60483 Re: jenkins role pattern regex not working , all projects are displayed attched video /screen shots Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203572.1576361374000.7614.1576362000262%40Atlassian.JIRA.
[JIRA] (JENKINS-60483) jenkins role pattern regex not working , all projects are displayed
Title: Message Title Kiran Singh Sathyanarayan updated an issue Jenkins / JENKINS-60483 jenkins role pattern regex not working , all projects are displayed Change By: Kiran Singh Sathyanarayan Attachment: unble_shows_all_projects_regx_not_applied-1.mp4 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203572.1576361374000.7616.1576362180154%40Atlassian.JIRA.
[JIRA] (JENKINS-60483) jenkins role pattern regex not working , all projects are displayed
Title: Message Title Kiran Singh Sathyanarayan updated an issue Jenkins / JENKINS-60483 jenkins role pattern regex not working , all projects are displayed Change By: Kiran Singh Sathyanarayan i wanted to display projects which starts only with helo / anible for particular user but its displaying all projects , can you help me out with regex pattrens patterns tried with helo-.* / Ansible-.* helo(.*) / after applying regex patterns all projects are displayed , find the attached screen shots one by one tried in all possible ways to resolve issue unable to show projects starts with helo /ansible find the video attached. Regards,Kiran [devopsksath...@gmail.com|mailto:devopsksath...@gmail.com]+91-9886370303 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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
[JIRA] (JENKINS-60483) jenkins role pattern regex not working , all projects are displayed
Title: Message Title Kiran Singh Sathyanarayan updated an issue Jenkins / JENKINS-60483 jenkins role pattern regex not working , all projects are displayed Change By: Kiran Singh Sathyanarayan Environment: windows 10 with Jenkins ver. 2.204 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203572.1576361374000.7620.1576362300280%40Atlassian.JIRA.
[JIRA] (JENKINS-60483) jenkins role pattern regex not working , all projects are displayed
Title: Message Title Kiran Singh Sathyanarayan updated an issue Jenkins / JENKINS-60483 jenkins role pattern regex not working , all projects are displayed Change By: Kiran Singh Sathyanarayan i wanted to display projects which starts only with helo / anible for particular user but its displaying all projects , can you help me out with regex patterns tried with helo-. * * / Ansible-.* * helo(.*) / *Ansible-(.*)* after applying regex patterns all projects are displayed , find the attached screen shots one by one tried in all possible ways to resolve issue unable to show projects starts with helo /ansible find the video attached. Regards,Kiran [devopsksath...@gmail.com|mailto:devopsksath...@gmail.com]+91-9886370303 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receivi
[JIRA] (JENKINS-60483) jenkins role pattern regex not working , all projects are displayed
Title: Message Title Kiran Singh Sathyanarayan updated an issue Jenkins / JENKINS-60483 jenkins role pattern regex not working , all projects are displayed Change By: Kiran Singh Sathyanarayan i wanted to display projects which starts only with helo / anible for particular user jenkins1 to show only particular projects but its displaying all projects when particular user logs in , can you help me out with regex patterns tried with helo-. * * * / Ansible-.** helo(.*) / *Ansible-(.*)* after applying regex patterns all projects are displayed , find the attached screen shots one by one tried in all possible ways to resolve issue unable to show projects starts with helo /ansible find the video attached. Regards,Kiran [devopsksath...@gmail.com|mailto:devopsksath...@gmail.com]+91-9886370303 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Je
[JIRA] (JENKINS-60483) jenkins role pattern regex not working , all projects are displayed
Title: Message Title Kiran Singh Sathyanarayan updated an issue Jenkins / JENKINS-60483 jenkins role pattern regex not working , all projects are displayed Change By: Kiran Singh Sathyanarayan i wanted to display projects which starts only with helo / anible for particular user jenkins1 to show only particular projects but its displaying all projects when particular user logs in , can you help me out with regex patterns tried with helo-. * * * / Ansible-.** helo(.*) / * *Ansible-(. * )* after applying regex patterns all projects are displayed , find the attached screen shots one by one tried in all possible ways to resolve issue unable to show projects starts with helo /ansible find the video attached. Regards,Kiran [devopsksath...@gmail.com|mailto:devopsksath...@gmail.com]+91-9886370303 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups
[JIRA] (JENKINS-60393) cloudbees-folder circular dependency
Title: Message Title Mark Waite commented on JENKINS-60393 Re: cloudbees-folder circular dependency My startup is not blocked, but I can definitely see the error in the log consistently with the cloudbees folder plugin 6.10.0 as represented in the 291e29a264 commit on the lts-plugins branch of my docker-lfs repository. Steps to duplicate the problem using that repository: Clone the docker image repository with the commands: $ git clone -o public -b lts-with-plugins https://github.com/MarkEWaite/docker-lfs.git $ cd docker-lfs $ git remote add upstream https://github.com/jenkinsci/docker.git $ git pull --all $ git checkout -b lts -t public/lts $ git checkout lts-with-plugins $ ./docker_build.py $ ./docker_run.py --clean --quiet Connect to the URL of that server (port 8080 on current host) Install CloudBees Folder plugin 6.10.0 Restart Jenkins, watch for the stack trace message Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-60484) Blue Ocean organization folder job can't be parsed by 2.204.1-rc build
Title: Message Title Mark Waite created an issue Jenkins / JENKINS-60484 Blue Ocean organization folder job can't be parsed by 2.204.1-rc build Issue Type: Bug Assignee: Unassigned Components: core Created: 2019-12-15 01:53 Environment: Jenkins 2.204.1-rc using the base image I maintain in docker-lfs plus credentials, agents, folders, and more. See https://github.com/MarkEWaite/docker-lfs/commit/f6210350565726fbe86ec8970cf0c539b8f67fdb for details Labels: lts-candidate Priority: Major Reporter: Mark Waite A Blue Ocean organization folder that I had created long ago in my Jenkins instance is no longer readable in Jenkins 2.204.1-rc. It was readable and completely usable in Jenkins 2.190.3 and has been readable and usable since it was first created in June 2017. I believe that Organization Folders have been removed from Blue Ocean in an earlier release. I'm not sure why this is failing now, when the most recent update to the Blue Ocean plugins in my installation was 1 month ago (updating to 1.121.0) See https://github.com/MarkEWaite/docker-lfs/commit/f6210350565726fbe86ec8970cf0c539b8f67fdb for the details of the plugins installed in that environment and the steps needed to recreate the environment. I'm removing that Blue Ocean Organization Folder on the assumption that it was an accident that it continued to work for me after Organization Folders were removed from Blue Ocean. Should this be included in the upgrade guide to direct users to recreate their Blue Ocean Organization Folders as GitHub, BitBucket, Gitlab, or Gitea organization folders?
[JIRA] (JENKINS-60484) Blue Ocean organization folder job can't be parsed by 2.204.1-rc build
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-60484 Blue Ocean organization folder job can't be parsed by 2.204.1-rc build Change By: Mark Waite Attachment: config.xml Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203573.1576374806000.7641.1576374900068%40Atlassian.JIRA.
[JIRA] (JENKINS-60484) Blue Ocean organization folder job can't be parsed by 2.204.1-rc build
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-60484 Blue Ocean organization folder job can't be parsed by 2.204.1-rc build Change By: Mark Waite A Blue Ocean organization folder that I had created long ago in my Jenkins instance is no longer readable in Jenkins 2.204.1-rc. It was readable and completely usable in Jenkins 2.190.3 and has been readable and usable since it was first created in June 2017.I believe that Organization Folders have been removed from Blue Ocean in an earlier release. I'm not sure why this is failing now, when the most recent update to the Blue Ocean plugins in my installation was 1 month ago (updating to 1.121.0)See https://github.com/MarkEWaite/docker-lfs/commit/f6210350565726fbe86ec8970cf0c539b8f67fdb for the details of the plugins installed in that environment and the steps needed to recreate the environment.I'm removing that Blue Ocean Organization Folder on the assumption that it was an accident that it continued to work for me after Organization Folders were removed from Blue Ocean.Should this be included in the upgrade guide to direct users to recreate their Blue Ocean Organization Folders as GitHub, BitBucket, Gitlab, or Gitea organization folders? I've attached the example [^config.xml] file which shows the problem in my installation. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-60484) Blue Ocean organization folder job can't be parsed by 2.204.1-rc build
Title: Message Title
Mark Waite updated an issue
Jenkins / JENKINS-60484
Blue Ocean organization folder job can't be parsed by 2.204.1-rc build
Change By:
Mark Waite
A Blue Ocean organization folder that I had created long ago in my Jenkins instance is no longer readable in Jenkins 2.204.1-rc. It was readable and completely usable in Jenkins 2.190.3 and has been readable and usable since it was first created in June 2017.I believe that Organization Folders have been removed from Blue Ocean in an earlier release. I'm not sure why this is failing now, when the most recent update to the Blue Ocean plugins in my installation was 1 month ago (updating to 1.121.0)See https://github.com/MarkEWaite/docker-lfs/commit/f6210350565726fbe86ec8970cf0c539b8f67fdb for the details of the plugins installed in that environment and the steps needed to recreate the environment.I'm removing that Blue Ocean Organization Folder on the assumption that it was an accident that it continued to work for me after Organization Folders were removed from Blue Ocean.Should this be included in the upgrade guide to direct users to recreate their Blue Ocean Organization Folders as GitHub, BitBucket, Gitlab, or Gitea organization folders?I've attached the example [^config.xml] file which shows the problem in my installation. The failure message is:{noformat}2019-12-15 01:00:25.106+ [id=27]SEVERE jenkins.InitReactorRunner$1#onTaskFailed: Failed Loading item MarkEWaiteorg.xmlpull.v1.XmlPullParserException: expected: /jenkins.branch.OrganizationFolder read: properties (position:END_TAG @76:16 in java.io.InputStreamReader@3e5df622)at org.kxml2.io.KXmlParser.exception(Unknown Source)at org.kxml2.io.KXmlParser.error(Unknown Source)at org.kxml2.io.KXmlParser.parseEndTag(Unknown Source)at org.kxml2.io.KXmlParser.nextImpl(Unknown Source)at org.kxml2.io.KXmlParser.next(Unknown Source)at com.thoughtworks.xstream.io.xml.XppReader.pullNextEvent(XppReader.java:109)Caused: com.thoughtworks.xstream.io.StreamException: : expected: /jenkins.branch.OrganizationFolder read: properties (position:END_TAG @76:16 in java.io.InputStreamReader@3e5df622)at com.thoughtworks.xstream.io.xml.XppReader.pullNextEvent(XppReader.java:124)at com.thoughtworks.xstream.io.xml.AbstractPullReader.readRealEvent(AbstractPullReader.java:148)at com.thoughtworks.xstream.io.xml.AbstractPullReader.readEvent(AbstractPullReader.java:135)at com.thoughtworks.xstream.io.xml.AbstractPullReader.move(AbstractPullReader.java:118)at com.thoughtworks.xstream.io.xml.AbstractPullReader.moveUp(AbstractPullReader.java:113)at com.thoughtworks.xstream.io.ReaderWrapper.moveUp(ReaderWrapper.java:40)at com.thoughtworks.xstream.io.path.PathTrackingReader.moveUp(PathTrackingReader.java:42)at hudson.util.RobustReflectionConverter.doUnmarshal(RobustReflectionConverter.java:364)at hudson.util.RobustReflectionConverter.unmarshal(RobustReflectionConverter.java:268)
[JIRA] (JENKINS-60485) Maven job on repository with modules - in ALM Octane create pipeline dialog - each module is shown as job
Title: Message Title Radi Berkovich created an issue Jenkins / JENKINS-60485 Maven job on repository with modules - in ALM Octane create pipeline dialog - each module is shown as job Issue Type: Bug Assignee: Radi Berkovich Components: hp-application-automation-tools-plugin Created: 2019-12-15 06:09 Priority: Minor Reporter: Radi Berkovich Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-60485) Maven job on repository with modules - in ALM Octane create pipeline dialog - each module is shown as job
Title: Message Title Radi Berkovich updated an issue Jenkins / JENKINS-60485 Maven job on repository with modules - in ALM Octane create pipeline dialog - each module is shown as job Change By: Radi Berkovich Labels: 6.0.3-BETA Octane Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203574.1576390153000.7645.1576390200197%40Atlassian.JIRA.
[JIRA] (JENKINS-60486) Manual UFT discovery job in folder - doesnot publish… … found tests
Title: Message Title Radi Berkovich created an issue Jenkins / JENKINS-60486 Manual UFT discovery job in folder - doesnot publish… … found tests Issue Type: Bug Assignee: Radi Berkovich Components: hp-application-automation-tools-plugin Created: 2019-12-15 06:10 Priority: Minor Reporter: Radi Berkovich Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message becaus
[JIRA] (JENKINS-60486) Manual UFT discovery job in folder - doesnot publish… … found tests
Title: Message Title Radi Berkovich updated an issue Jenkins / JENKINS-60486 Manual UFT discovery job in folder - doesnot publish… … found tests Change By: Radi Berkovich Labels: 6.0.3-BETA Octane Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203575.1576390257000.7647.1576390320233%40Atlassian.JIRA.
[JIRA] (JENKINS-60486) Manual UFT discovery job in folder - doesnot publish found tests
Title: Message Title Radi Berkovich updated an issue Jenkins / JENKINS-60486 Manual UFT discovery job in folder - doesnot publish found tests Change By: Radi Berkovich Summary: Manual UFT discovery job in folder - doesnot publish … … found tests Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203575.1576390257000.7648.1576390320289%40Atlassian.JIRA.
[JIRA] (JENKINS-60487) Build failure analyzer plugin failed to identify failure causes
Title: Message Title Gajanan Mahajan created an issue Jenkins / JENKINS-60487 Build failure analyzer plugin failed to identify failure causes Issue Type: Bug Assignee: Tomas Westling Components: build-failure-analyzer-plugin Created: 2019-12-15 06:39 Priority: Critical Reporter: Gajanan Mahajan I am using Jenkins version 2.1999 and BFA version 1.24.1 and have a pipeline. We've defined some failure causes and when pipeline fails those failure causes are expected to identify but sometimes some of failure causes are identified and sometimes none is identified. I could not identify specific pattern for this. Also if same build is scanned across the defined failure causes those are identified. This is similar to issue JENKINS-42755 which has been fixed and closed. Add Comment
