[JIRA] (JENKINS-57776) Support kv2 version for vault secrets in Jenkins Pipeline
Title: Message Title sivanarayana baisani commented on JENKINS-57776 Re: Support kv2 version for vault secrets in Jenkins Pipeline yeah that would be most desirable thing to do to solve such issues with dependency between two plugins. 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.199723.1559281987000.1491.1573770600166%40Atlassian.JIRA.
[JIRA] (JENKINS-57961) Add ability to set nvm version for complete pipeline either in options or environment
Title: Message Title sivanarayana baisani commented on JENKINS-57961 Re: Add ability to set nvm version for complete pipeline either in options or environment configuring nvm version in individual box works but then if you have two pipelines which needs different versions of nvm its difficult to add nvm version of each stage for an entire pipeline where we have more than 10 applications built and deployed through a single pipeline on a single node. 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.199944.1560263593000.1487.1573770360323%40Atlassian.JIRA.
[JIRA] (JENKINS-57843) EC2 spot fleet Instances stay connected even after the cloud is deleted
Title: Message Title sivanarayana baisani closed an issue as Fixed Jenkins / JENKINS-57843 EC2 spot fleet Instances stay connected even after the cloud is deleted Change By: sivanarayana baisani Status: Open Closed 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199801.1559658452000.1489.1573770360348%40Atlassian.JIRA.
[JIRA] (JENKINS-58819) When a Jenkins job with no agent or wrong agent is executed, the EC2 fleet plugin is spinning up all the possible instances in all the clouds configured with different Agent Lab
Title: Message Title sivanarayana baisani closed an issue as Cannot Reproduce Jenkins / JENKINS-58819 When a Jenkins job with no agent or wrong agent is executed, the EC2 fleet plugin is spinning up all the possible instances in all the clouds configured with different Agent Labels Change By: sivanarayana baisani Status: Open Closed Resolution: Cannot Reproduce 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.201131.1565037052000.1481.1573770120420%40Atlassian.JIRA.
[JIRA] (JENKINS-49627) Last Changes Plugin shows git changes only in the first directory of the multidirectory pipeline
Title: Message Title sivanarayana baisani commented on JENKINS-49627 Re: Last Changes Plugin shows git changes only in the first directory of the multidirectory pipeline any progress with the multi repo support for this plugin? 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.188552.1519051579000.3503.1572275820269%40Atlassian.JIRA.
[JIRA] (JENKINS-58832) Artifact-promotion plugin is searching for metadata.xml file in a wrong path
Title: Message Title sivanarayana baisani created an issue Jenkins / JENKINS-58832 Artifact-promotion plugin is searching for metadata.xml file in a wrong path Issue Type: Bug Assignee: Unassigned Components: artifact-promotion-plugin Created: 2019-08-06 17:15 Environment: Artifact-promotion plugin 0.5.2, Jenkins 2.176.2 Labels: plugin Priority: Blocker Reporter: sivanarayana baisani The plugin is searching for the metadata.xml file inside the snapshot directory but it should be searching in the application repository. The error seems like Something has gone wrong and the transfer has failed: Could not find metadata com.company:App:1.0-SNAPSHOT/maven-metadata.xml in stagingrepo but it should search at com.company:App/maven-metadata.xml Add Comment
[JIRA] (JENKINS-58819) When a Jenkins job with no agent or wrong agent is executed, the EC2 fleet plugin is spinning up all the possible instances in all the clouds configured with different Agent Lab
Title: Message Title sivanarayana baisani created an issue Jenkins / JENKINS-58819 When a Jenkins job with no agent or wrong agent is executed, the EC2 fleet plugin is spinning up all the possible instances in all the clouds configured with different Agent Labels Issue Type: Bug Assignee: Chad Schmutzer Components: ec2-fleet-plugin Created: 2019-08-05 20:30 Environment: jenkins 2.176.2, EC2-fleet-jenkins-plugin 1.10.0 Labels: plugin Priority: Major Reporter: sivanarayana baisani If we have 4 EC2 spot fleet clouds configured to spin a maximum of 20 instances based on the agent label specified, if a jenkins job with no agent specified is executed, the build stays in the queue searching for agents and this is triggering all the 20 possible instances. Expected result would be to spin the instance only if the label assigned to the cloud is matched with the label specified in the Job
[JIRA] (JENKINS-57842) Ec2-fleet Autoscaling Description
Title: Message Title sivanarayana baisani updated JENKINS-57842 Jenkins / JENKINS-57842 Ec2-fleet Autoscaling Description Change By: sivanarayana baisani Status: Open Fixed but Unreleased Resolution: Done 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199800.1559657538000.8400.1561471981629%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57842) Ec2-fleet Autoscaling Description
Title: Message Title sivanarayana baisani updated JENKINS-57842 Jenkins / JENKINS-57842 Ec2-fleet Autoscaling Description Change By: sivanarayana baisani Status: Fixed but Unreleased Resolved 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199800.1559657538000.8402.1561471981838%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37984) org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
Title: Message Title sivanarayana baisani edited a comment on JENKINS-37984 Re: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script I have a strange scenario with this error. So I have jobs which are huge in size the 1st job is about 1200 lines long and it works completely fine and the 2nd job is about 850 lines and it got this error. And by removing some lines from the code worked fine. I added the same code again adding stage by stage and it worked fine again. It's the same code, same number of lines nothing changed but different behaviors. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.174127.1473169024000.3967.1560975781789%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37984) org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
Title: Message Title sivanarayana baisani updated an issue Jenkins / JENKINS-37984 org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script Change By: sivanarayana baisani Priority: Major Blocker 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.174127.1473169024000.3859.1560975422878%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37984) org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
Title: Message Title sivanarayana baisani edited a comment on JENKINS-37984 Re: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script I have a strange scenario with this error. So I have jobs which are huge in size the 1st job is about 1200 lines long and it works completely fine and the 2nd job is about 850 lines and it got this error. And by removing some lines from the code worked 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.174127.1473169024000.3804.1560975360944%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37984) org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
Title: Message Title sivanarayana baisani commented on JENKINS-37984 Re: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script I have a strange scenario with this error. So I have jobs which are huge in size the 1st job is about 1200 lines long and it works completely fine and the 2nd job is about 850 lines and it got this error. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.174127.1473169024000.3802.1560975302337%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58077) ${STAGE_NAME} variable doesn't get the stage name in a checkout block
Title: Message Title
sivanarayana baisani closed an issue as Not A Defect
found a different work flow
Jenkins / JENKINS-58077
${STAGE_NAME} variable doesn't get the stage name in a checkout block
Change By:
sivanarayana baisani
Status:
Open 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200102.156087558.2746.1560877980250%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58077) ${STAGE_NAME} variable doesn't get the stage name in a checkout block
Title: Message Title
sivanarayana baisani updated an issue
Jenkins / JENKINS-58077
${STAGE_NAME} variable doesn't get the stage name in a checkout block
Change By:
sivanarayana baisani
the ${STAGE_NAME} variable doesn't work in a checkout scm block but works fine with regular 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200102.156087558.2667.1560876060059%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58077) ${STAGE_NAME} variable doesn't get the stage name in a checkout block
Title: Message Title
sivanarayana baisani created an issue
Jenkins / JENKINS-58077
${STAGE_NAME} variable doesn't get the stage name in a checkout block
Issue Type:
Bug
Assignee:
Unassigned
Components:
pipeline
Created:
2019-06-18 16:33
Priority:
Major
Reporter:
sivanarayana baisani
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200102.156087558.2631.1560875640134%40Atlassian.JIRA.
For more options, visit
[JIRA] (JENKINS-57961) Add ability to set nvm version for complete pipeline either in options or environment
Title: Message Title sivanarayana baisani created an issue Jenkins / JENKINS-57961 Add ability to set nvm version for complete pipeline either in options or environment Issue Type: New Feature Assignee: Tomas Salazar Components: nvm-wrapper-plugin Created: 2019-06-11 14:33 Labels: plugin Priority: Major Reporter: sivanarayana baisani Its very difficult to give the .nvm version for a pipeline that have multiple stages where the nvm version is to be defined. So it would be good if we have an option to set the version for complete pipeline Add Comment
[JIRA] (JENKINS-57843) EC2 spot fleet Instances stay connected even after the cloud is deleted
Title: Message Title sivanarayana baisani created an issue Jenkins / JENKINS-57843 EC2 spot fleet Instances stay connected even after the cloud is deleted Issue Type: Bug Assignee: Chad Schmutzer Components: ec2-fleet-plugin Created: 2019-06-04 14:27 Labels: plugin ec2-fleet Priority: Major Reporter: sivanarayana baisani The instances stay connected to jenkins master even after the ec2-spot fleet cloud is deleted. Now, the only way to remove these instances is removing them manually in the Nodes section. I expect the nodes to get disconnected when a cloud is deleted. Add Comment
[JIRA] (JENKINS-57842) Ec2-fleet Autoscaling Description
Title: Message Title sivanarayana baisani created an issue Jenkins / JENKINS-57842 Ec2-fleet Autoscaling Description Issue Type: Task Assignee: Chad Schmutzer Components: ec2-fleet-plugin, pipeline Created: 2019-06-04 14:12 Priority: Minor Reporter: sivanarayana baisani There is no proper description about how the autoscaling works with EC2 fleet plugin and how it should be configured in AWS. More description will be helpful Add Comment This message was sent by Atlassian Jira
[JIRA] (JENKINS-57776) Support kv2 version for vault secrets in Jenkins Pipeline
Title: Message Title sivanarayana baisani updated an issue Jenkins / JENKINS-57776 Support kv2 version for vault secrets in Jenkins Pipeline Change By: sivanarayana baisani The present Hashicorp Vault Pipeline Plugin depend on Hashicorp Vault Plugin. The Hashicorp Vault Plugin was modified to support KV2 secrets from vault but don't have a release that include the feature. And we also need the support for this feature in the Hashicorp Vault Pipeline plugin as well to be able to use the feature in a 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199723.1559281987000.19922.1559586180261%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57776) Support kv2 version for vault secrets in Jenkins Pipeline
Title: Message Title sivanarayana baisani created an issue Jenkins / JENKINS-57776 Support kv2 version for vault secrets in Jenkins Pipeline Issue Type: New Feature Assignee: Phil Madden Components: hashicorp-vault-pipeline-plugin Created: 2019-05-31 05:53 Labels: plugin pipeline jenkins plugins vault Priority: Major Reporter: sivanarayana baisani The present Hashicorp Vault Pipeline Plugin depend on Hashicorp Vault Plugin. The Hashicorp Vault Plugin was modified to support KV2 secrets from vault but don't have a release that include the feature. And we also need the support for this feature in the Hashicorp Vault Pipeline plugin as well to be able to use the feature in a Jenkinsfile. Add Comment
