Re: Design Discussion: External Fingerprint Storage for Jenkins

[Jesse Glick]

On Thu, Mar 19, 2020 at 5:29 PM Sumit Sarin
 wrote:
> Multiple instances may work on updating/deleting/adding facets at the same 
> time.

Then include the Jenkins instance ID as part of the database key for
facet metadata.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr3Q7r8y9YxaP6SmVLnA0vaSyq%2BFW1Sq8D1ZayjTZrosug%40mail.gmail.com.

Design Discussion: External Fingerprint Storage for Jenkins

[Sumit Sarin]

Hi Everyone,
It would be amazing to get some community feedback on a design decision. I 
am working on Externalizing Fingerprint Storage of Jenkins, and I wish to 
allow a common external storage across multiple Jenkins instances. This 
would allow a much richer experience in tracking fingerprints (think 
artifacts, credentials, docker containers, etc.) across the entire CI/CD 
flow.

Currently, in a non distributed environment, a local XML-based database is 
used to store the fingerprints. When a fingerprint is brought from the disk 
into memory, we ensure that for each unique fingerprint, only one object of 
it is present in memory. Any and all changes happen to the same object, 
which subsequently overwrites itself to the XML database at the end of the 
day. 

But in a distributed environment, where there are multiple Jenkins 
instances storing fingerprints on a single external storage, it becomes 
challenging to ensure data consistency. Multiple instances may work on 
updating/deleting/adding facets at the same time. Moreover, these changes 
can happen by different plugins, making it hard to track when and what kind 
a change in attribute is about to happen. 

To solve this problem, the most promising solution that I can see is that I 
use a very similar design as the current offering, and ensure that a lock 
allows a fingerprint to enter the memory of only a single Jenkins instance. 
The lock would ensure that at a time only one Jenkins instance has the 
right to read or write to a particular fingerprint. This completely solves 
data inconsistency problems, while at the same time it also ensures 
simplicity and no change (or very less) to the current Fingerprint API 
architecture. However, it comes with the drawback that it is extra strict 
in allowing access, and would block a lot of other Jenkins instances, often 
unnecessarily (performance bottleneck).

What would be your thoughts on this? I could really benefit from some 
insights/feedback/comments on this.

Thanks and Regards,
Sumit Sarin

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/e0f2f445-41c4-4d3b-b02b-ce25fe976637%40googlegroups.com.

Re: [GSOC 2020 PROJECT IDEA] Jenkins distribution customize service

[Lee Meador]

How does this tool interleave with version updates?

What if the package requires plugin A, version 2.0 and plugin B, version
3.0. Plugin A, version 2.0 requires a minimum Jenkins version of 2.x but
plugin B, version 3.0 does not work with Jenkins version 2.x?

This has a couple of solutions I can think of:
1) The team supporting a package has to release a new version of the
package for new versions of Jenkins itself. I suppose it could be required
for every LTS version or the package would be marked unsupported for the
Jenkins version.
2) The package could supply minimum and maximum plugin versions that all
work together no matter which combination of versions are loaded. Or,
similarly, there could be a list of acceptable versions for each plugin.

This would be easier to think about if I knew more about the way Jenkins
decides which versions of plugins are offered for loading in Manage Jenkins
> Manage Plugins. Perhaps it could cooperate with the

On Tue, Mar 17, 2020 at 12:30 PM Sladyn Nunes 
wrote:

> I was discussing with @FelixQueiruga on the UX Sig channel regarding reuse
> of the jenkins core to generate the forms for the UI for each plugin but I
> guess that option is not very viable, since it would prevent update to the
> forms and any such update would bring down our distribution service, we
> therefore currently stand with the option to  generate the fields using the
> json schema that JCasC uses but that is not very reliable.  I was wondering
> if we could scan all the DataBound Constructors and generate as many fields
> as we can, but I guess that is too much overhead. I would love to get some
> thoughts on this. Feel free to add your reply here or in the docs.
> The link to this section in the proposal is here :
> https://docs.google.com/document/d/1C7VQJ92Yhr0KRDcNVHYxn4ri7OL9IGZmgxY6UFON6-g/edit?disco=JMf0sg0
>
> Thanks and Cheers
> Sladyn
>
> On Wednesday, January 8, 2020 at 8:19:32 PM UTC+5:30, Rick wrote:
>>
>> Hi team,
>>
>> I'd like to share an idea with you. There are some original discussions
>> from the GSoC thread
>> 
>> here.
>>
>> For many users, they download Jenkins first, then select some plugins and
>> config them. It might take a lot of time, like hours. But if we can get a
>> perfect Jenkins distribution which contains all we need, it can save that
>> time for us. Yes, I propose an out of the box solution.
>>
>> The service could be like this, a website offered as
>> https://customize.jenkins.io. Plus, it should be self-host. People can
>> select the following configurations:
>>
>>- Jenkins core version
>>- plugins
>>- common configuration, user/password, update-center site e.g.
>>- plugin based configuration, Kubernetes, Sonarqube plugin config e.g.
>>- multi-form package, jenkins.war or docker image
>>- other things
>>
>> Two projects are expected backend and frontend. I think
>> https://github.com/jenkinsci/custom-war-packager already did a lot of
>> works. We can reuse it in this project. The backend should provide the
>> modern Restful API. We can start the backend project with SpringBoot, it
>> can save a lot of time.
>>
>> About the frontend project, I don't have too many experiences on it. For
>> example, we can start it by React framework. If you're instrested in it,
>> please help to add more ideas on it.
>>
>> Any feedbacks are very appreciated.
>>
>> Best regards,
>> Rick
>> --
>> Zhao Xiaojie (Rick)
>> Blog: https://github.com/LinuxSuRen
>> Twitter: https://twitter.com/suren69811254
>>
>> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/34c9dbcc-086d-45f5-b372-89367114ce6c%40googlegroups.com
> 
> .
>


-- 
-- Lee Meador
Sent from gmail. My real email address is lee AT leemeador.com

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAA4vtDRmMLrrVSPypcYowFJZyNm7sgK5VeF76NiL_VRzJKFiuw%40mail.gmail.com.

Re: Plugin release issue

[selva vignesh]

https://github.com/jenkins-infra/repository-permissions-updater/pull/1439

This the request which i made

On Thu, Mar 19, 2020 at 4:18 PM selva vignesh 
wrote:

> Hi Richard,
> Yes i have raised the pull request and my yml (plugin-zohosprints.yml) has
> been merged with the *repository-permissions-updater* repo.
>
> when access
> https://repo.jenkins-ci.org/releases/io/jenkins/plugins/zohosprints/ this
> url getting below error.
>
> {
> "errors": [
> {
> "status": 404,
> "message": "{\"error\":\"Item
> releases:io/jenkins/plugins/zohosprints does not exist\"}"
> }
> ]
> }
>
>
> Do i need to do anything? kindly assist
>
> On Thu, Mar 19, 2020 at 4:12 PM Richard Bywater 
> wrote:
>
>> Have you followed the instructions at
>> https://github.com/jenkins-infra/repository-permissions-updater/ to get
>> your user permissions to perform the upload into the release repository?
>>
>> Richard.
>>
>> On Thu, 19 Mar 2020 at 23:24, selva vignesh 
>> wrote:
>>
>>> Hi,
>>>
>>> [INFO] --- maven-deploy-plugin:2.8.2:deploy (default-deploy) @
>>> zohosprints ---
>>>
>>> Uploading to maven.jenkins-ci.org:
>>> https://repo.jenkins-ci.org/releases/io/jenkins/plugins/zohosprints/1.0/zohosprints-1.0.hpi
>>>
>>> Uploading to maven.jenkins-ci.org:
>>> https://repo.jenkins-ci.org/releases/io/jenkins/plugins/zohosprints/1.0/zohosprints-1.0.pom
>>>
>>> [INFO]
>>> 
>>>
>>> [INFO] BUILD FAILURE
>>>
>>> [INFO]
>>> 
>>>
>>> [INFO] Total time:  01:03 min
>>>
>>> [INFO] Finished at: 2020-03-19T15:44:58+05:30
>>>
>>> [INFO]
>>> 
>>>
>>> [ERROR] Failed to execute goal
>>> org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy)
>>> on project zohosprints: Failed to deploy artifacts: Could not transfer
>>> artifact io.jenkins.plugins:zohosprints:hpi:1.0 from/to
>>> maven.jenkins-ci.org (https://repo.jenkins-ci.org/releases/): Access
>>> denied to:
>>> https://repo.jenkins-ci.org/releases/io/jenkins/plugins/zohosprints/1.0/zohosprints-1.0.hpi
>>> -> [Help 1]
>>>
>>> [ERROR]
>>>
>>> [ERROR] To see the full stack trace of the errors, re-run Maven
>>> with the -e switch.
>>>
>>> [ERROR] Re-run Maven using the -X switch to enable full debug
>>> logging.
>>>
>>> [ERROR]
>>>
>>> [ERROR] For more information about the errors and possible
>>> solutions, please read the following articles:
>>>
>>> [ERROR] [Help 1]
>>> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
>>>
>>> [INFO]
>>> 
>>>
>>> [INFO] BUILD FAILURE
>>>
>>> [INFO]
>>> 
>>>
>>> [INFO] Total time:  03:54 min
>>>
>>> [INFO] Finished at: 2020-03-19T15:44:58+05:30
>>>
>>> I have done needed changes and now getting this error as Access denied.
>>> I have added encrypted credential in my system under ~/.m2/settings.xml.
>>> Kindly assist.
>>> On Thu, Mar 19, 2020 at 1:04 PM Richard Bywater 
>>> wrote:
>>>
 Further to Gavin's advice I would ensure that the tag matches the
 version number of the plugin release you are making so that future people
 can easily see what the source code looked like for, say, v1.2 of the
 plugin release.

 Richard

 On Thu, 19 Mar 2020, 8:32 PM 'Gavin Mogan' via Jenkins Developers, <
 jenkinsci-dev@googlegroups.com> wrote:

> Googling a bit after reading the git tag man page like it suggested.
> https://git-scm.com/docs/git-check-ref-format
>
> Tag really should be single unique ASCII word.
>
> So "beta" might work once, but you really want "1.1.0-beta" or
> something.
>
> If it contains alpha or beta it'll go into the experimental update
> center -
> https://jenkins.io/doc/developer/publishing/releasing-experimental-updates/
>
> On Thu., Mar. 19, 2020, 12:27 a.m. selva vignesh, <
> selvavignesh...@gmail.com> wrote:
>
>> [INFO] Scanning for projects...
>>
>> [INFO]
>>
>> [INFO] ---< io.jenkins.plugins:zohosprints
>> >---
>>
>> [INFO] Building Zoho Sprints 1.0
>>
>> [INFO] [ hpi
>> ]-
>>
>> [INFO]
>>
>> [INFO] --- maven-release-plugin:2.5.3:prepare (default-cli) @
>> zohosprints ---
>>
>> [INFO] Resuming release from phase 'scm-tag'
>>
>> [INFO] Tagging release with the label beta release...
>>
>> [INFO] Executing: /bin/sh -c cd
>> /Users/selva-5820/jenkinsgithubrepo/zohosprints-plugin && git tag -F
>> /var/folders/z4/7mg5vgwd1jb4zj9p61kckypdwhyjwq/T/maven-scm-1664433616.commit
>> 

Re: Plugin release issue

[selva vignesh]

Hi Richard,
Yes i have raised the pull request and my yml (plugin-zohosprints.yml) has
been merged with the *repository-permissions-updater* repo.

when access
https://repo.jenkins-ci.org/releases/io/jenkins/plugins/zohosprints/ this
url getting below error.

{
"errors": [
{
"status": 404,
"message": "{\"error\":\"Item
releases:io/jenkins/plugins/zohosprints does not exist\"}"
}
]
}


Do i need to do anything? kindly assist

On Thu, Mar 19, 2020 at 4:12 PM Richard Bywater  wrote:

> Have you followed the instructions at
> https://github.com/jenkins-infra/repository-permissions-updater/ to get
> your user permissions to perform the upload into the release repository?
>
> Richard.
>
> On Thu, 19 Mar 2020 at 23:24, selva vignesh 
> wrote:
>
>> Hi,
>>
>> [INFO] --- maven-deploy-plugin:2.8.2:deploy (default-deploy) @
>> zohosprints ---
>>
>> Uploading to maven.jenkins-ci.org:
>> https://repo.jenkins-ci.org/releases/io/jenkins/plugins/zohosprints/1.0/zohosprints-1.0.hpi
>>
>> Uploading to maven.jenkins-ci.org:
>> https://repo.jenkins-ci.org/releases/io/jenkins/plugins/zohosprints/1.0/zohosprints-1.0.pom
>>
>> [INFO]
>> 
>>
>> [INFO] BUILD FAILURE
>>
>> [INFO]
>> 
>>
>> [INFO] Total time:  01:03 min
>>
>> [INFO] Finished at: 2020-03-19T15:44:58+05:30
>>
>> [INFO]
>> 
>>
>> [ERROR] Failed to execute goal
>> org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy)
>> on project zohosprints: Failed to deploy artifacts: Could not transfer
>> artifact io.jenkins.plugins:zohosprints:hpi:1.0 from/to
>> maven.jenkins-ci.org (https://repo.jenkins-ci.org/releases/): Access
>> denied to:
>> https://repo.jenkins-ci.org/releases/io/jenkins/plugins/zohosprints/1.0/zohosprints-1.0.hpi
>> -> [Help 1]
>>
>> [ERROR]
>>
>> [ERROR] To see the full stack trace of the errors, re-run Maven with
>> the -e switch.
>>
>> [ERROR] Re-run Maven using the -X switch to enable full debug
>> logging.
>>
>> [ERROR]
>>
>> [ERROR] For more information about the errors and possible
>> solutions, please read the following articles:
>>
>> [ERROR] [Help 1]
>> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
>>
>> [INFO]
>> 
>>
>> [INFO] BUILD FAILURE
>>
>> [INFO]
>> 
>>
>> [INFO] Total time:  03:54 min
>>
>> [INFO] Finished at: 2020-03-19T15:44:58+05:30
>>
>> I have done needed changes and now getting this error as Access denied.
>> I have added encrypted credential in my system under ~/.m2/settings.xml.
>> Kindly assist.
>> On Thu, Mar 19, 2020 at 1:04 PM Richard Bywater 
>> wrote:
>>
>>> Further to Gavin's advice I would ensure that the tag matches the
>>> version number of the plugin release you are making so that future people
>>> can easily see what the source code looked like for, say, v1.2 of the
>>> plugin release.
>>>
>>> Richard
>>>
>>> On Thu, 19 Mar 2020, 8:32 PM 'Gavin Mogan' via Jenkins Developers, <
>>> jenkinsci-dev@googlegroups.com> wrote:
>>>
 Googling a bit after reading the git tag man page like it suggested.
 https://git-scm.com/docs/git-check-ref-format

 Tag really should be single unique ASCII word.

 So "beta" might work once, but you really want "1.1.0-beta" or
 something.

 If it contains alpha or beta it'll go into the experimental update
 center -
 https://jenkins.io/doc/developer/publishing/releasing-experimental-updates/

 On Thu., Mar. 19, 2020, 12:27 a.m. selva vignesh, <
 selvavignesh...@gmail.com> wrote:

> [INFO] Scanning for projects...
>
> [INFO]
>
> [INFO] ---< io.jenkins.plugins:zohosprints
> >---
>
> [INFO] Building Zoho Sprints 1.0
>
> [INFO] [ hpi
> ]-
>
> [INFO]
>
> [INFO] --- maven-release-plugin:2.5.3:prepare (default-cli) @
> zohosprints ---
>
> [INFO] Resuming release from phase 'scm-tag'
>
> [INFO] Tagging release with the label beta release...
>
> [INFO] Executing: /bin/sh -c cd
> /Users/selva-5820/jenkinsgithubrepo/zohosprints-plugin && git tag -F
> /var/folders/z4/7mg5vgwd1jb4zj9p61kckypdwhyjwq/T/maven-scm-1664433616.commit
> 'beta release'
>
> [INFO] Working directory:
> /Users/selva-5820/jenkinsgithubrepo/zohosprints-plugin
>
> [INFO]
> 
>
> [INFO] BUILD FAILURE
>
> [INFO]
> 

Re: Plugin release issue

[Richard Bywater]

Have you followed the instructions at
https://github.com/jenkins-infra/repository-permissions-updater/ to get
your user permissions to perform the upload into the release repository?

Richard.

On Thu, 19 Mar 2020 at 23:24, selva vignesh 
wrote:

> Hi,
>
> [INFO] --- maven-deploy-plugin:2.8.2:deploy (default-deploy) @ zohosprints
> ---
>
> Uploading to maven.jenkins-ci.org:
> https://repo.jenkins-ci.org/releases/io/jenkins/plugins/zohosprints/1.0/zohosprints-1.0.hpi
>
> Uploading to maven.jenkins-ci.org:
> https://repo.jenkins-ci.org/releases/io/jenkins/plugins/zohosprints/1.0/zohosprints-1.0.pom
>
> [INFO]
> 
>
> [INFO] BUILD FAILURE
>
> [INFO]
> 
>
> [INFO] Total time:  01:03 min
>
> [INFO] Finished at: 2020-03-19T15:44:58+05:30
>
> [INFO]
> 
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy)
> on project zohosprints: Failed to deploy artifacts: Could not transfer
> artifact io.jenkins.plugins:zohosprints:hpi:1.0 from/to
> maven.jenkins-ci.org (https://repo.jenkins-ci.org/releases/): Access
> denied to:
> https://repo.jenkins-ci.org/releases/io/jenkins/plugins/zohosprints/1.0/zohosprints-1.0.hpi
> -> [Help 1]
>
> [ERROR]
>
> [ERROR] To see the full stack trace of the errors, re-run Maven with
> the -e switch.
>
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>
> [ERROR]
>
> [ERROR] For more information about the errors and possible solutions,
> please read the following articles:
>
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
>
> [INFO]
> 
>
> [INFO] BUILD FAILURE
>
> [INFO]
> 
>
> [INFO] Total time:  03:54 min
>
> [INFO] Finished at: 2020-03-19T15:44:58+05:30
>
> I have done needed changes and now getting this error as Access denied.
> I have added encrypted credential in my system under ~/.m2/settings.xml.
> Kindly assist.
> On Thu, Mar 19, 2020 at 1:04 PM Richard Bywater 
> wrote:
>
>> Further to Gavin's advice I would ensure that the tag matches the version
>> number of the plugin release you are making so that future people can
>> easily see what the source code looked like for, say, v1.2 of the plugin
>> release.
>>
>> Richard
>>
>> On Thu, 19 Mar 2020, 8:32 PM 'Gavin Mogan' via Jenkins Developers, <
>> jenkinsci-dev@googlegroups.com> wrote:
>>
>>> Googling a bit after reading the git tag man page like it suggested.
>>> https://git-scm.com/docs/git-check-ref-format
>>>
>>> Tag really should be single unique ASCII word.
>>>
>>> So "beta" might work once, but you really want "1.1.0-beta" or something.
>>>
>>> If it contains alpha or beta it'll go into the experimental update
>>> center -
>>> https://jenkins.io/doc/developer/publishing/releasing-experimental-updates/
>>>
>>> On Thu., Mar. 19, 2020, 12:27 a.m. selva vignesh, <
>>> selvavignesh...@gmail.com> wrote:
>>>
 [INFO] Scanning for projects...

 [INFO]

 [INFO] ---< io.jenkins.plugins:zohosprints
 >---

 [INFO] Building Zoho Sprints 1.0

 [INFO] [ hpi
 ]-

 [INFO]

 [INFO] --- maven-release-plugin:2.5.3:prepare (default-cli) @
 zohosprints ---

 [INFO] Resuming release from phase 'scm-tag'

 [INFO] Tagging release with the label beta release...

 [INFO] Executing: /bin/sh -c cd
 /Users/selva-5820/jenkinsgithubrepo/zohosprints-plugin && git tag -F
 /var/folders/z4/7mg5vgwd1jb4zj9p61kckypdwhyjwq/T/maven-scm-1664433616.commit
 'beta release'

 [INFO] Working directory:
 /Users/selva-5820/jenkinsgithubrepo/zohosprints-plugin

 [INFO]
 

 [INFO] BUILD FAILURE

 [INFO]
 

 [INFO] Total time:  1.666 s

 [INFO] Finished at: 2020-03-19T12:52:30+05:30

 [INFO]
 

 [ERROR] Failed to execute goal
 org.apache.maven.plugins:maven-release-plugin:2.5.3:prepare
 (default-cli) on project zohosprints: Unable to tag SCM

 [ERROR] Provider message:

 [ERROR] The git-tag command failed.

 [ERROR] Command output:

 [ERROR] fatal: 'beta release' is not a valid tag name.

 [ERROR]

 [ERROR] -> [Help 1]

 [ERROR]

 [ERROR] To see the full stack trace of the errors, re-run 

Re: Plugin release issue

[selva vignesh]

Hi,

[INFO] --- maven-deploy-plugin:2.8.2:deploy (default-deploy) @ zohosprints
---

Uploading to maven.jenkins-ci.org:
https://repo.jenkins-ci.org/releases/io/jenkins/plugins/zohosprints/1.0/zohosprints-1.0.hpi

Uploading to maven.jenkins-ci.org:
https://repo.jenkins-ci.org/releases/io/jenkins/plugins/zohosprints/1.0/zohosprints-1.0.pom

[INFO]


[INFO] BUILD FAILURE

[INFO]


[INFO] Total time:  01:03 min

[INFO] Finished at: 2020-03-19T15:44:58+05:30

[INFO]


[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy)
on project zohosprints: Failed to deploy artifacts: Could not transfer
artifact io.jenkins.plugins:zohosprints:hpi:1.0 from/to maven.jenkins-ci.org
(https://repo.jenkins-ci.org/releases/): Access denied to:
https://repo.jenkins-ci.org/releases/io/jenkins/plugins/zohosprints/1.0/zohosprints-1.0.hpi
-> [Help 1]

[ERROR]

[ERROR] To see the full stack trace of the errors, re-run Maven with
the -e switch.

[ERROR] Re-run Maven using the -X switch to enable full debug logging.

[ERROR]

[ERROR] For more information about the errors and possible solutions,
please read the following articles:

[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException

[INFO]


[INFO] BUILD FAILURE

[INFO]


[INFO] Total time:  03:54 min

[INFO] Finished at: 2020-03-19T15:44:58+05:30

I have done needed changes and now getting this error as Access denied.
I have added encrypted credential in my system under ~/.m2/settings.xml.
Kindly assist.
On Thu, Mar 19, 2020 at 1:04 PM Richard Bywater  wrote:

> Further to Gavin's advice I would ensure that the tag matches the version
> number of the plugin release you are making so that future people can
> easily see what the source code looked like for, say, v1.2 of the plugin
> release.
>
> Richard
>
> On Thu, 19 Mar 2020, 8:32 PM 'Gavin Mogan' via Jenkins Developers, <
> jenkinsci-dev@googlegroups.com> wrote:
>
>> Googling a bit after reading the git tag man page like it suggested.
>> https://git-scm.com/docs/git-check-ref-format
>>
>> Tag really should be single unique ASCII word.
>>
>> So "beta" might work once, but you really want "1.1.0-beta" or something.
>>
>> If it contains alpha or beta it'll go into the experimental update center
>> -
>> https://jenkins.io/doc/developer/publishing/releasing-experimental-updates/
>>
>> On Thu., Mar. 19, 2020, 12:27 a.m. selva vignesh, <
>> selvavignesh...@gmail.com> wrote:
>>
>>> [INFO] Scanning for projects...
>>>
>>> [INFO]
>>>
>>> [INFO] ---< io.jenkins.plugins:zohosprints
>>> >---
>>>
>>> [INFO] Building Zoho Sprints 1.0
>>>
>>> [INFO] [ hpi
>>> ]-
>>>
>>> [INFO]
>>>
>>> [INFO] --- maven-release-plugin:2.5.3:prepare (default-cli) @
>>> zohosprints ---
>>>
>>> [INFO] Resuming release from phase 'scm-tag'
>>>
>>> [INFO] Tagging release with the label beta release...
>>>
>>> [INFO] Executing: /bin/sh -c cd
>>> /Users/selva-5820/jenkinsgithubrepo/zohosprints-plugin && git tag -F
>>> /var/folders/z4/7mg5vgwd1jb4zj9p61kckypdwhyjwq/T/maven-scm-1664433616.commit
>>> 'beta release'
>>>
>>> [INFO] Working directory:
>>> /Users/selva-5820/jenkinsgithubrepo/zohosprints-plugin
>>>
>>> [INFO]
>>> 
>>>
>>> [INFO] BUILD FAILURE
>>>
>>> [INFO]
>>> 
>>>
>>> [INFO] Total time:  1.666 s
>>>
>>> [INFO] Finished at: 2020-03-19T12:52:30+05:30
>>>
>>> [INFO]
>>> 
>>>
>>> [ERROR] Failed to execute goal
>>> org.apache.maven.plugins:maven-release-plugin:2.5.3:prepare
>>> (default-cli) on project zohosprints: Unable to tag SCM
>>>
>>> [ERROR] Provider message:
>>>
>>> [ERROR] The git-tag command failed.
>>>
>>> [ERROR] Command output:
>>>
>>> [ERROR] fatal: 'beta release' is not a valid tag name.
>>>
>>> [ERROR]
>>>
>>> [ERROR] -> [Help 1]
>>>
>>> [ERROR]
>>>
>>> [ERROR] To see the full stack trace of the errors, re-run Maven with
>>> the -e switch.
>>>
>>> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>>>
>>> [ERROR]
>>>
>>> [ERROR] For more information about the errors and possible solutions,
>>> please read the following articles:
>>>
>>> [ERROR] [Help 1]
>>> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
>>>
>>> After the all change getting error like this. what might be the git-tag.
>>> I gave as *beta 

Re: Plugin release issue

[Richard Bywater]

Further to Gavin's advice I would ensure that the tag matches the version
number of the plugin release you are making so that future people can
easily see what the source code looked like for, say, v1.2 of the plugin
release.

Richard

On Thu, 19 Mar 2020, 8:32 PM 'Gavin Mogan' via Jenkins Developers, <
jenkinsci-dev@googlegroups.com> wrote:

> Googling a bit after reading the git tag man page like it suggested.
> https://git-scm.com/docs/git-check-ref-format
>
> Tag really should be single unique ASCII word.
>
> So "beta" might work once, but you really want "1.1.0-beta" or something.
>
> If it contains alpha or beta it'll go into the experimental update center
> -
> https://jenkins.io/doc/developer/publishing/releasing-experimental-updates/
>
> On Thu., Mar. 19, 2020, 12:27 a.m. selva vignesh, <
> selvavignesh...@gmail.com> wrote:
>
>> [INFO] Scanning for projects...
>>
>> [INFO]
>>
>> [INFO] ---< io.jenkins.plugins:zohosprints
>> >---
>>
>> [INFO] Building Zoho Sprints 1.0
>>
>> [INFO] [ hpi
>> ]-
>>
>> [INFO]
>>
>> [INFO] --- maven-release-plugin:2.5.3:prepare (default-cli) @ zohosprints
>> ---
>>
>> [INFO] Resuming release from phase 'scm-tag'
>>
>> [INFO] Tagging release with the label beta release...
>>
>> [INFO] Executing: /bin/sh -c cd
>> /Users/selva-5820/jenkinsgithubrepo/zohosprints-plugin && git tag -F
>> /var/folders/z4/7mg5vgwd1jb4zj9p61kckypdwhyjwq/T/maven-scm-1664433616.commit
>> 'beta release'
>>
>> [INFO] Working directory:
>> /Users/selva-5820/jenkinsgithubrepo/zohosprints-plugin
>>
>> [INFO]
>> 
>>
>> [INFO] BUILD FAILURE
>>
>> [INFO]
>> 
>>
>> [INFO] Total time:  1.666 s
>>
>> [INFO] Finished at: 2020-03-19T12:52:30+05:30
>>
>> [INFO]
>> 
>>
>> [ERROR] Failed to execute goal
>> org.apache.maven.plugins:maven-release-plugin:2.5.3:prepare (default-cli)
>> on project zohosprints: Unable to tag SCM
>>
>> [ERROR] Provider message:
>>
>> [ERROR] The git-tag command failed.
>>
>> [ERROR] Command output:
>>
>> [ERROR] fatal: 'beta release' is not a valid tag name.
>>
>> [ERROR]
>>
>> [ERROR] -> [Help 1]
>>
>> [ERROR]
>>
>> [ERROR] To see the full stack trace of the errors, re-run Maven with the
>> -e switch.
>>
>> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>>
>> [ERROR]
>>
>> [ERROR] For more information about the errors and possible solutions,
>> please read the following articles:
>>
>> [ERROR] [Help 1]
>> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
>>
>> After the all change getting error like this. what might be the git-tag.
>> I gave as *beta release*
>> Kindly assist
>> On Mon, Mar 16, 2020 at 7:26 PM Slide  wrote:
>>
>>> You need to have a -SNAPSHOT version in your pom.xml. The version for
>>> the release will be asked for during the release process. See
>>> https://github.com/jenkinsci/email-ext-plugin/blob/master/pom.xml#L20 for
>>> an example.
>>>
>>> On Mon, Mar 16, 2020 at 5:45 AM selva vignesh 
>>> wrote:
>>>
 Hi team,
 When i am performing release getting below error can anyone please
 assist me.

 I've added *Artifactory Credentials for Maven. *

 *mvn release:prepare release:perform*


 [INFO] Scanning for projects...

 [INFO]

 [INFO] ---< io.jenkins.plugins:zohosprints
 >---

 [INFO] Building Zoho Sprints 1.1

 [INFO] [ hpi
 ]-

 [INFO]

 [INFO] --- maven-release-plugin:2.5.3:prepare (default-cli) @
 zohosprints ---

 [INFO]
 

 [INFO] BUILD FAILURE

 [INFO]
 

 [INFO] Total time:  1.994 s

 [INFO] Finished at: 2020-03-16T18:11:02+05:30

 [INFO]
 

 [ERROR] Failed to execute goal
 org.apache.maven.plugins:maven-release-plugin:2.5.3:prepare
 (default-cli) on project zohosprints: You don't have a SNAPSHOT
 project in the reactor projects list. -> [Help 1]

 [ERROR]

 [ERROR] To see the full stack trace of the errors, re-run Maven with
 the -e switch.

 [ERROR] Re-run Maven using the -X switch to enable full debug logging.

 [ERROR]

 [ERROR] For more information about the errors and possible solutions,
 please read the following articles:

 [ERROR] [Help 1]
 http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException

 --
 You received this message 

Re: Plugin release issue

['Gavin Mogan' via Jenkins Developers]

Googling a bit after reading the git tag man page like it suggested.
https://git-scm.com/docs/git-check-ref-format

Tag really should be single unique ASCII word.

So "beta" might work once, but you really want "1.1.0-beta" or something.

If it contains alpha or beta it'll go into the experimental update center -
https://jenkins.io/doc/developer/publishing/releasing-experimental-updates/

On Thu., Mar. 19, 2020, 12:27 a.m. selva vignesh, 
wrote:

> [INFO] Scanning for projects...
>
> [INFO]
>
> [INFO] ---< io.jenkins.plugins:zohosprints
> >---
>
> [INFO] Building Zoho Sprints 1.0
>
> [INFO] [ hpi
> ]-
>
> [INFO]
>
> [INFO] --- maven-release-plugin:2.5.3:prepare (default-cli) @ zohosprints
> ---
>
> [INFO] Resuming release from phase 'scm-tag'
>
> [INFO] Tagging release with the label beta release...
>
> [INFO] Executing: /bin/sh -c cd
> /Users/selva-5820/jenkinsgithubrepo/zohosprints-plugin && git tag -F
> /var/folders/z4/7mg5vgwd1jb4zj9p61kckypdwhyjwq/T/maven-scm-1664433616.commit
> 'beta release'
>
> [INFO] Working directory:
> /Users/selva-5820/jenkinsgithubrepo/zohosprints-plugin
>
> [INFO]
> 
>
> [INFO] BUILD FAILURE
>
> [INFO]
> 
>
> [INFO] Total time:  1.666 s
>
> [INFO] Finished at: 2020-03-19T12:52:30+05:30
>
> [INFO]
> 
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-release-plugin:2.5.3:prepare (default-cli)
> on project zohosprints: Unable to tag SCM
>
> [ERROR] Provider message:
>
> [ERROR] The git-tag command failed.
>
> [ERROR] Command output:
>
> [ERROR] fatal: 'beta release' is not a valid tag name.
>
> [ERROR]
>
> [ERROR] -> [Help 1]
>
> [ERROR]
>
> [ERROR] To see the full stack trace of the errors, re-run Maven with the
> -e switch.
>
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>
> [ERROR]
>
> [ERROR] For more information about the errors and possible solutions,
> please read the following articles:
>
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
>
> After the all change getting error like this. what might be the git-tag.
> I gave as *beta release*
> Kindly assist
> On Mon, Mar 16, 2020 at 7:26 PM Slide  wrote:
>
>> You need to have a -SNAPSHOT version in your pom.xml. The version for the
>> release will be asked for during the release process. See
>> https://github.com/jenkinsci/email-ext-plugin/blob/master/pom.xml#L20 for
>> an example.
>>
>> On Mon, Mar 16, 2020 at 5:45 AM selva vignesh 
>> wrote:
>>
>>> Hi team,
>>> When i am performing release getting below error can anyone please
>>> assist me.
>>>
>>> I've added *Artifactory Credentials for Maven. *
>>>
>>> *mvn release:prepare release:perform*
>>>
>>>
>>> [INFO] Scanning for projects...
>>>
>>> [INFO]
>>>
>>> [INFO] ---< io.jenkins.plugins:zohosprints
>>> >---
>>>
>>> [INFO] Building Zoho Sprints 1.1
>>>
>>> [INFO] [ hpi
>>> ]-
>>>
>>> [INFO]
>>>
>>> [INFO] --- maven-release-plugin:2.5.3:prepare (default-cli) @
>>> zohosprints ---
>>>
>>> [INFO]
>>> 
>>>
>>> [INFO] BUILD FAILURE
>>>
>>> [INFO]
>>> 
>>>
>>> [INFO] Total time:  1.994 s
>>>
>>> [INFO] Finished at: 2020-03-16T18:11:02+05:30
>>>
>>> [INFO]
>>> 
>>>
>>> [ERROR] Failed to execute goal
>>> org.apache.maven.plugins:maven-release-plugin:2.5.3:prepare
>>> (default-cli) on project zohosprints: You don't have a SNAPSHOT project
>>> in the reactor projects list. -> [Help 1]
>>>
>>> [ERROR]
>>>
>>> [ERROR] To see the full stack trace of the errors, re-run Maven with
>>> the -e switch.
>>>
>>> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>>>
>>> [ERROR]
>>>
>>> [ERROR] For more information about the errors and possible solutions,
>>> please read the following articles:
>>>
>>> [ERROR] [Help 1]
>>> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Jenkins Developers" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to jenkinsci-dev+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-dev/f5184842-53d4-4d8c-be29-bcbc8a5f4321%40googlegroups.com
>>> 
>>> .
>>>
>>
>>
>> --
>> Website: 

Re: Plugin release issue

[Raihaan Shouhell]

git tags cannot take spaces IIRC pick a name without a space

Cheers,
Raihaan

On Thu, Mar 19, 2020 at 3:26 PM selva vignesh 
wrote:

> [INFO] Scanning for projects...
>
> [INFO]
>
> [INFO] ---< io.jenkins.plugins:zohosprints
> >---
>
> [INFO] Building Zoho Sprints 1.0
>
> [INFO] [ hpi
> ]-
>
> [INFO]
>
> [INFO] --- maven-release-plugin:2.5.3:prepare (default-cli) @ zohosprints
> ---
>
> [INFO] Resuming release from phase 'scm-tag'
>
> [INFO] Tagging release with the label beta release...
>
> [INFO] Executing: /bin/sh -c cd
> /Users/selva-5820/jenkinsgithubrepo/zohosprints-plugin && git tag -F
> /var/folders/z4/7mg5vgwd1jb4zj9p61kckypdwhyjwq/T/maven-scm-1664433616.commit
> 'beta release'
>
> [INFO] Working directory:
> /Users/selva-5820/jenkinsgithubrepo/zohosprints-plugin
>
> [INFO]
> 
>
> [INFO] BUILD FAILURE
>
> [INFO]
> 
>
> [INFO] Total time:  1.666 s
>
> [INFO] Finished at: 2020-03-19T12:52:30+05:30
>
> [INFO]
> 
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-release-plugin:2.5.3:prepare (default-cli)
> on project zohosprints: Unable to tag SCM
>
> [ERROR] Provider message:
>
> [ERROR] The git-tag command failed.
>
> [ERROR] Command output:
>
> [ERROR] fatal: 'beta release' is not a valid tag name.
>
> [ERROR]
>
> [ERROR] -> [Help 1]
>
> [ERROR]
>
> [ERROR] To see the full stack trace of the errors, re-run Maven with the
> -e switch.
>
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>
> [ERROR]
>
> [ERROR] For more information about the errors and possible solutions,
> please read the following articles:
>
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
>
> After the all change getting error like this. what might be the git-tag.
> I gave as *beta release*
> Kindly assist
> On Mon, Mar 16, 2020 at 7:26 PM Slide  wrote:
>
>> You need to have a -SNAPSHOT version in your pom.xml. The version for the
>> release will be asked for during the release process. See
>> https://github.com/jenkinsci/email-ext-plugin/blob/master/pom.xml#L20 for
>> an example.
>>
>> On Mon, Mar 16, 2020 at 5:45 AM selva vignesh 
>> wrote:
>>
>>> Hi team,
>>> When i am performing release getting below error can anyone please
>>> assist me.
>>>
>>> I've added *Artifactory Credentials for Maven. *
>>>
>>> *mvn release:prepare release:perform*
>>>
>>>
>>> [INFO] Scanning for projects...
>>>
>>> [INFO]
>>>
>>> [INFO] ---< io.jenkins.plugins:zohosprints
>>> >---
>>>
>>> [INFO] Building Zoho Sprints 1.1
>>>
>>> [INFO] [ hpi
>>> ]-
>>>
>>> [INFO]
>>>
>>> [INFO] --- maven-release-plugin:2.5.3:prepare (default-cli) @
>>> zohosprints ---
>>>
>>> [INFO]
>>> 
>>>
>>> [INFO] BUILD FAILURE
>>>
>>> [INFO]
>>> 
>>>
>>> [INFO] Total time:  1.994 s
>>>
>>> [INFO] Finished at: 2020-03-16T18:11:02+05:30
>>>
>>> [INFO]
>>> 
>>>
>>> [ERROR] Failed to execute goal
>>> org.apache.maven.plugins:maven-release-plugin:2.5.3:prepare
>>> (default-cli) on project zohosprints: You don't have a SNAPSHOT project
>>> in the reactor projects list. -> [Help 1]
>>>
>>> [ERROR]
>>>
>>> [ERROR] To see the full stack trace of the errors, re-run Maven with
>>> the -e switch.
>>>
>>> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>>>
>>> [ERROR]
>>>
>>> [ERROR] For more information about the errors and possible solutions,
>>> please read the following articles:
>>>
>>> [ERROR] [Help 1]
>>> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Jenkins Developers" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to jenkinsci-dev+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-dev/f5184842-53d4-4d8c-be29-bcbc8a5f4321%40googlegroups.com
>>> 
>>> .
>>>
>>
>>
>> --
>> Website: http://earl-of-code.com
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Jenkins Developers" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to jenkinsci-dev+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> 

Re: Plugin release issue

[selva vignesh]

[INFO] Scanning for projects...

[INFO]

[INFO] ---< io.jenkins.plugins:zohosprints
>---

[INFO] Building Zoho Sprints 1.0

[INFO] [ hpi
]-

[INFO]

[INFO] --- maven-release-plugin:2.5.3:prepare (default-cli) @ zohosprints
---

[INFO] Resuming release from phase 'scm-tag'

[INFO] Tagging release with the label beta release...

[INFO] Executing: /bin/sh -c cd
/Users/selva-5820/jenkinsgithubrepo/zohosprints-plugin && git tag -F
/var/folders/z4/7mg5vgwd1jb4zj9p61kckypdwhyjwq/T/maven-scm-1664433616.commit
'beta release'

[INFO] Working directory:
/Users/selva-5820/jenkinsgithubrepo/zohosprints-plugin

[INFO]


[INFO] BUILD FAILURE

[INFO]


[INFO] Total time:  1.666 s

[INFO] Finished at: 2020-03-19T12:52:30+05:30

[INFO]


[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-release-plugin:2.5.3:prepare (default-cli)
on project zohosprints: Unable to tag SCM

[ERROR] Provider message:

[ERROR] The git-tag command failed.

[ERROR] Command output:

[ERROR] fatal: 'beta release' is not a valid tag name.

[ERROR]

[ERROR] -> [Help 1]

[ERROR]

[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.

[ERROR] Re-run Maven using the -X switch to enable full debug logging.

[ERROR]

[ERROR] For more information about the errors and possible solutions,
please read the following articles:

[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException

After the all change getting error like this. what might be the git-tag.
I gave as *beta release*
Kindly assist
On Mon, Mar 16, 2020 at 7:26 PM Slide  wrote:

> You need to have a -SNAPSHOT version in your pom.xml. The version for the
> release will be asked for during the release process. See
> https://github.com/jenkinsci/email-ext-plugin/blob/master/pom.xml#L20 for
> an example.
>
> On Mon, Mar 16, 2020 at 5:45 AM selva vignesh 
> wrote:
>
>> Hi team,
>> When i am performing release getting below error can anyone please assist
>> me.
>>
>> I've added *Artifactory Credentials for Maven. *
>>
>> *mvn release:prepare release:perform*
>>
>>
>> [INFO] Scanning for projects...
>>
>> [INFO]
>>
>> [INFO] ---< io.jenkins.plugins:zohosprints
>> >---
>>
>> [INFO] Building Zoho Sprints 1.1
>>
>> [INFO] [ hpi
>> ]-
>>
>> [INFO]
>>
>> [INFO] --- maven-release-plugin:2.5.3:prepare (default-cli) @ zohosprints
>> ---
>>
>> [INFO]
>> 
>>
>> [INFO] BUILD FAILURE
>>
>> [INFO]
>> 
>>
>> [INFO] Total time:  1.994 s
>>
>> [INFO] Finished at: 2020-03-16T18:11:02+05:30
>>
>> [INFO]
>> 
>>
>> [ERROR] Failed to execute goal
>> org.apache.maven.plugins:maven-release-plugin:2.5.3:prepare (default-cli)
>> on project zohosprints: You don't have a SNAPSHOT project in the reactor
>> projects list. -> [Help 1]
>>
>> [ERROR]
>>
>> [ERROR] To see the full stack trace of the errors, re-run Maven with the
>> -e switch.
>>
>> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>>
>> [ERROR]
>>
>> [ERROR] For more information about the errors and possible solutions,
>> please read the following articles:
>>
>> [ERROR] [Help 1]
>> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Jenkins Developers" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to jenkinsci-dev+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-dev/f5184842-53d4-4d8c-be29-bcbc8a5f4321%40googlegroups.com
>> 
>> .
>>
>
>
> --
> Website: http://earl-of-code.com
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CAPiUgVeexZrvEkzRXM517z_5c%3D24X9VpqMStv5%3DfkX4CNBwueg%40mail.gmail.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google