[JIRA] (JENKINS-32793) POSTing to pluginManager/installNecessaryPlugins to install an older version of a plugin than the latest version will unexpectedly install the latest version
Title: Message Title Rami Abughazaleh commented on JENKINS-32793 Re: POSTing to pluginManager/installNecessaryPlugins to install an older version of a plugin than the latest version will unexpectedly install the latest version I was originally able to work-around the problem my directly uploading the plugin file to http://localhost:8080/jenkins/pluginManager/uploadPlugin Someone posted an article with some sample code: https://chburmeister.github.io/2017/04/08/deploy-specific-versions-of-jenkins-plugins-via-artifactory-caching.html 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.167948.1454644069000.17472.1563769620348%40Atlassian.JIRA.
[JIRA] (JENKINS-32793) POSTing to pluginManager/installNecessaryPlugins to install an older version of a plugin than the latest version will unexpectedly install the latest version
Title: Message Title Rami Abughazaleh edited a comment on JENKINS-32793 Re: POSTing to pluginManager/installNecessaryPlugins to install an older version of a plugin than the latest version will unexpectedly install the latest version I was originally able to work-around the problem my by directly uploading the plugin file to [http://localhost:8080/jenkins/pluginManager/uploadPlugin]Someone posted an article with some sample code: [ https://chburmeister.github.io/2017/04/08/deploy-specific-versions-of-jenkins-plugins-via-artifactory-caching.html ] 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.167948.1454644069000.17473.1563769620396%40Atlassian.JIRA.
[JIRA] (JENKINS-33119) Ability to set the assembly copyright value in the AssemblyVersionInfo.cs file
Title: Message Title Rami Abughazaleh commented on JENKINS-33119 Re: Ability to set the assembly copyright value in the AssemblyVersionInfo.cs file Unfortunately, that plugin doesn't support setting the copyright field. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] [versionnumber-plugin] (JENKINS-33119) Ability to set the assembly copyright value in the AssemblyVersionInfo.cs file
Title: Message Title
Rami Abughazaleh created an issue
Jenkins / JENKINS-33119
Ability to set the assembly copyright value in the AssemblyVersionInfo.cs file
Issue Type:
New Feature
Assignee:
Unassigned
Components:
versionnumber-plugin
Created:
24/Feb/16 7:50 AM
Environment:
Jenkins 1.646 Version Number Plug-In v1.6
Priority:
Minor
Reporter:
Rami Abughazaleh
I'd like to request the ability to set the assembly copyright value in the AssemblyVersionInfo.cs file.
In this way, the current year can be set in this field.
For example, "Copyright 2015-$ {CURRENT_YEAR}
MyCompany".
Thank you.
[JIRA] [versionnumber-plugin] (JENKINS-33119) Ability to set the assembly copyright value in the AssemblyVersionInfo.cs file
Title: Message Title Rami Abughazaleh updated an issue Jenkins / JENKINS-33119 Ability to set the assembly copyright value in the AssemblyVersionInfo.cs file Change By: Rami Abughazaleh Labels: plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [tfs-plugin] (JENKINS-10960) TFS plugin should consider NO_CI flag
Title: Message Title Rami Abughazaleh commented on JENKINS-10960 Re: TFS plugin should consider NO_CI flag For reference, there's already a pull request here: https://github.com/jenkinsci/tfs-plugin/pull/9 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [tfs-plugin] (JENKINS-29408) Support building shelvesets
Title: Message Title Rami Abughazaleh commented on JENKINS-29408 Re: Support building shelvesets For reference, there's already a pull request here: https://github.com/jenkinsci/tfs-plugin/pull/63 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-32793) POSTing to pluginManager/installNecessaryPlugins to install an older version of a plugin than the latest version will unexpectedly install the latest version
Title: Message Title Rami Abughazaleh commented on JENKINS-32793 Re: POSTing to pluginManager/installNecessaryPlugins to install an older version of a plugin than the latest version will unexpectedly install the latest version The reason I want to install an older plugin is because the new version of the plugin caused some issues and we cannot move forward with it until those issues are fixed for example. Is there a work-around to installing an older version of a plugin programmatically? Thank you. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-32793) POSTing to pluginManager/installNecessaryPlugins to install an older version of a plugin than the latest version will unexpectedly install the latest version
Title: Message Title Rami Abughazaleh commented on JENKINS-32793 Re: POSTing to pluginManager/installNecessaryPlugins to install an older version of a plugin than the latest version will unexpectedly install the latest version Thank you! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-32793) POSTing to pluginManager/installNecessaryPlugins to install an older version of a plugin than the latest version will unexpectedly install the latest version
Title: Message Title
Rami Abughazaleh updated an issue
Jenkins / JENKINS-32793
POSTing to pluginManager/installNecessaryPlugins to install an older version of a plugin than the latest version will unexpectedly install the latest version
Change By:
Rami Abughazaleh
POSTing to pluginManager/installNecessaryPlugins to install an older version of a plugin than the latest version will unexpectedly install the latest version.For example, the latest version of the tfs plugin is 4.0, but I can't install an older version (ex. 3.2):{code}curl -X POST -d "
[JIRA] [core] (JENKINS-32793) POSTing to pluginManager/installNecessaryPlugins to install an older version of a plugin than the latest version will unexpectedly install the latest version
Title: Message Title
Rami Abughazaleh updated an issue
Jenkins / JENKINS-32793
POSTing to pluginManager/installNecessaryPlugins to install an older version of a plugin than the latest version will unexpectedly install the latest version
Change By:
Rami Abughazaleh
POSTing to pluginManager/installNecessaryPlugins to install an older version of a plugin than the latest version will unexpectedly install the latest version.For example, the latest version of the tfs plugin is 4.0, but I can't install an older version (ex. 3.2): ``` {code} curl -X POST -d "
[JIRA] [core] (JENKINS-32793) POSTing to pluginManager/installNecessaryPlugins to install an older version of a plugin than the latest version will unexpectedly install the latest version
Title: Message Title Rami Abughazaleh created an issue Jenkins / JENKINS-32793 POSTing to pluginManager/installNecessaryPlugins to install an older version of a plugin than the latest version will unexpectedly install the latest version Issue Type: Bug Assignee: Unassigned Components: core Created: 05/Feb/16 3:47 AM Environment: Jenkins 1.646 Windows Server 2012 R2 Priority: Minor Reporter: Rami Abughazaleh POSTing to pluginManager/installNecessaryPlugins to install an older version of a plugin than the latest version will unexpectedly install the latest version. For example, the latest version of the tfs plugin is 4.0, but I can't install an older version (ex. 3.2): ``` curl -X POST -d "" --header "Content-Type: text/xml" http://192.168.0.175:8080/pluginManager/installNecessaryPlugins ``` The tfs plugin 4.0 is installed anyway. I don't think any workarounds exist.
[JIRA] [tfs-plugin] (JENKINS-32784) Update the "Integration Build" field in associated TFS work items
Title: Message Title Rami Abughazaleh created an issue Jenkins / JENKINS-32784 Update the "Integration Build" field in associated TFS work items Issue Type: New Feature Assignee: redsolo Attachments: buildquality1.png Components: tfs-plugin Created: 04/Feb/16 8:00 PM Environment: Jenkins 1.646 Team Foundation Server Plug-in 3.2.0 Version Number Plug-In 1.6 Priority: Minor Reporter: Rami Abughazaleh Thank you for tfs-plugin. I would like for Jenkins to optionally associate work-items with the build so that the "Integration Build" field is updated with the build identifier (ex. build version number). Thank you.
[JIRA] [versionnumber-plugin] (JENKINS-32736) Ability to support simple arithmetic with the build version number
Title: Message Title
Rami Abughazaleh created an issue
Jenkins / JENKINS-32736
Ability to support simple arithmetic with the build version number
Issue Type:
Bug
Assignee:
Unassigned
Components:
versionnumber-plugin
Created:
02/Feb/16 10:28 PM
Environment:
Jenkins 1.646 Version Number Plug-In v1.6
Labels:
plugins
Priority:
Minor
Reporter:
Rami Abughazaleh
Thank you for the versionnumber Jenkins plugin.
I would like the versionnumber Jenkins plugin to support simple arithmetic to calculate the build version number.
An example version number format string: 1.0.(1200 * $ {YEARS_SINCE_PROJECT_START}
) + $ {BUILD_MONTH, X}
$ {BUILD_DAY, XX}
.$ {BUILDS_TODAY, X}
In this way, if my project started in 2015, the last build in that year would have a version
[JIRA] [versionnumber-plugin] (JENKINS-32736) Ability to support simple arithmetic with the build version number
Title: Message Title
Rami Abughazaleh updated an issue
Jenkins / JENKINS-32736
Ability to support simple arithmetic with the build version number
Change By:
Rami Abughazaleh
Thank you for the versionnumber Jenkins plugin.I would like the versionnumber Jenkins plugin to support simple arithmetic to calculate the build version number.An example version number format string: {code:java} 1.0.(1200 * ${YEARS_SINCE_PROJECT_START}) + ${BUILD_MONTH, X}${BUILD_DAY, XX}.${BUILDS_TODAY, X} {code} In this way, if my project started in 2015, the last build in that year would have a version number of 1.0.1231.1 for example.And then instead of having to increment the minor version number, the next build in the new year would be 1.0.1301.1 for example.It doesn't seem that the plugin currently supports this.Thank you.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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] [envinject-plugin] (JENKINS-30069) versionnumber plugin should resolve vars from "envinject" plugin
Title: Message Title Rami Abughazaleh commented on JENKINS-30069 Re: versionnumber plugin should resolve vars from "envinject" plugin Here's what worked for me: 1. Install the "Pre SCM BuildStep Plugin" 2. Enable to "Run buildstep before SCM runs" in job configuration 3. Add a build step "Inject environment variables" within the "Pre SCM BuildStep" 4. Now you can use the environment variable in the "Version Number Format String" Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [envinject-plugin] (JENKINS-30069) versionnumber plugin should resolve vars from "envinject" plugin
Title: Message Title Rami Abughazaleh updated an issue Jenkins / JENKINS-30069 versionnumber plugin should resolve vars from "envinject" plugin Change By: Rami Abughazaleh Comment: Here's what worked for me:1. Install the "Pre SCM BuildStep Plugin"2. Enable to "Run buildstep before SCM runs" in job configuration3. Add a build step "Inject environment variables" within the "Pre SCM BuildStep"4. Now you can use the environment variable in the "Version Number Format String" Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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.
