How to enable Travis CI for jenkins plugin repo

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
21 messages Options
12
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

How to enable Travis CI for jenkins plugin repo

Andrey Pohilko-2
Hi,

I'm the maintainer for performance-plugin repo.

I'm trying to use my typical approach with controlling the project quality using GitHub+TravisCI+Codecov integration, which proven its value for me. However, I'm missing the admin right on repo to enable TravisCI for it. Can anybody help me enabling it? I don't need the admin rights per se, just need to enable TravisCI for it.

https://travis-ci.org/jenkinsci/performance-plugin

--
Andrey

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/d43f9a06-568c-4d29-995f-e182f093a703%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: How to enable Travis CI for jenkins plugin repo

Kanstantsin Shautsou-2
Try contact INFRA team and ask them to provide admin access to your plugin. 

On Wednesday, July 6, 2016 at 12:12:07 PM UTC+3, Andrey Pohilko wrote:
Hi,

I'm the maintainer for performance-plugin repo.

I'm trying to use my typical approach with controlling the project quality using GitHub+TravisCI+Codecov integration, which proven its value for me. However, I'm missing the admin right on repo to enable TravisCI for it. Can anybody help me enabling it? I don't need the admin rights per se, just need to enable TravisCI for it.

<a href="https://travis-ci.org/jenkinsci/performance-plugin" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Ftravis-ci.org%2Fjenkinsci%2Fperformance-plugin\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHLPhYEm90yuueoPSz43BdGIkfutQ&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Ftravis-ci.org%2Fjenkinsci%2Fperformance-plugin\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHLPhYEm90yuueoPSz43BdGIkfutQ&#39;;return true;">https://travis-ci.org/jenkinsci/performance-plugin

--
Andrey

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/7e51e25d-cf8c-4494-b503-300e7f52f4f2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: How to enable Travis CI for jenkins plugin repo

Daniel Beck
In reply to this post by Andrey Pohilko-2
Done.

> On 06.07.2016, at 11:12, Andrey Pohilko <[hidden email]> wrote:
>
> Can anybody help me enabling it?

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/139AE438-020A-420A-B655-A76BBACEEF43%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: How to enable Travis CI for jenkins plugin repo

Liam Newman
In reply to this post by Andrey Pohilko-2
Andrey, 
What does running in TravisCI provide that is not already in the jenkinsci.org build?  Just wondering.

Thanks!
Liam Newman

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/dd684a61-61cd-4d8e-bbf7-c7965949e32e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: How to enable Travis CI for jenkins plugin repo

Kanstantsin Shautsou-2
Ability to configure build process, ability to set credentials and upload something to external services, etc.

On Jul 16, 2016, at 00:35, Liam Newman <[hidden email]> wrote:

Andrey, 
What does running in TravisCI provide that is not already in the jenkinsci.org build?  Just wondering.

Thanks!
Liam Newman


--
You received this message because you are subscribed to a topic in the Google Groups "Jenkins Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-dev/n3b2LbHeV6Y/unsubscribe.
To unsubscribe from this group and all its topics, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/dd684a61-61cd-4d8e-bbf7-c7965949e32e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/65E4F229-7B99-41D5-A889-3931E0EE23C7%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

signature.asc (859 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: How to enable Travis CI for jenkins plugin repo

Kohsuke Kawaguchi
Administrator
In reply to this post by Andrey Pohilko-2
So in this case the motivation is to activate Codecov.io on plugins. On https://jenkins.ci.cloudbees.com/job/plugins/ we use templating so that we only need to change the setting once to impact every plugin.

If we make that change across the board, would that make you happy enough to stop the use of Travis? It seems like it's a relatively easy change to make it happen, and I think it'd benefit everyone.

I'm asking because I think it sends a wrong signal when we are using Travis for something Jenkins does just as well.

On Wed, Jul 6, 2016 at 2:12 AM Andrey Pohilko <[hidden email]> wrote:
Hi,

I'm the maintainer for performance-plugin repo.

I'm trying to use my typical approach with controlling the project quality using GitHub+TravisCI+Codecov integration, which proven its value for me. However, I'm missing the admin right on repo to enable TravisCI for it. Can anybody help me enabling it? I don't need the admin rights per se, just need to enable TravisCI for it.

https://travis-ci.org/jenkinsci/performance-plugin

--
Andrey

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/d43f9a06-568c-4d29-995f-e182f093a703%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAN4CQ4xaX%2BMp8es0%3DdkR01ychfL1JTxinPj%2BA0BYLpD5hnWOBQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: How to enable Travis CI for jenkins plugin repo

Kanstantsin Shautsou-2
Jenkins CloudBees doesn’t provide any ways to control or configure build process and integrations. In 2016 that’s blocker for development. Also you can’t do anything with reviewable.io because you have no analogues.

On Jul 20, 2016, at 23:51, Kohsuke Kawaguchi <[hidden email]> wrote:

So in this case the motivation is to activate Codecov.io on plugins. On https://jenkins.ci.cloudbees.com/job/plugins/ we use templating so that we only need to change the setting once to impact every plugin.

If we make that change across the board, would that make you happy enough to stop the use of Travis? It seems like it's a relatively easy change to make it happen, and I think it'd benefit everyone.

I'm asking because I think it sends a wrong signal when we are using Travis for something Jenkins does just as well.

On Wed, Jul 6, 2016 at 2:12 AM Andrey Pohilko <[hidden email]> wrote:
Hi,

I'm the maintainer for performance-plugin repo.

I'm trying to use my typical approach with controlling the project quality using GitHub+TravisCI+Codecov integration, which proven its value for me. However, I'm missing the admin right on repo to enable TravisCI for it. Can anybody help me enabling it? I don't need the admin rights per se, just need to enable TravisCI for it.

https://travis-ci.org/jenkinsci/performance-plugin

--
Andrey

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/d43f9a06-568c-4d29-995f-e182f093a703%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to a topic in the Google Groups "Jenkins Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-dev/n3b2LbHeV6Y/unsubscribe.
To unsubscribe from this group and all its topics, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAN4CQ4xaX%2BMp8es0%3DdkR01ychfL1JTxinPj%2BA0BYLpD5hnWOBQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/A0AE4D84-52CC-497C-AF71-2D8389FC921D%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

signature.asc (859 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: How to enable Travis CI for jenkins plugin repo

Kohsuke Kawaguchi
Administrator
Jenkins does provide a way to configure the build process, for example via Jenkinsfile, via Job DSL plugin, etc.

Like I said in my previous email, it's just that in jenkins.io.cloudbees.com we choose to use a template to lock things down.

IIUC reviewable.io is orthogonal to this. That's between GitHub and it.

On Wed, Jul 20, 2016 at 1:55 PM Kanstantsin Shautsou <[hidden email]> wrote:
Jenkins CloudBees doesn’t provide any ways to control or configure build process and integrations. In 2016 that’s blocker for development. Also you can’t do anything with reviewable.io because you have no analogues.

On Jul 20, 2016, at 23:51, Kohsuke Kawaguchi <[hidden email]> wrote:

So in this case the motivation is to activate Codecov.io on plugins. On https://jenkins.ci.cloudbees.com/job/plugins/ we use templating so that we only need to change the setting once to impact every plugin.

If we make that change across the board, would that make you happy enough to stop the use of Travis? It seems like it's a relatively easy change to make it happen, and I think it'd benefit everyone.

I'm asking because I think it sends a wrong signal when we are using Travis for something Jenkins does just as well.

On Wed, Jul 6, 2016 at 2:12 AM Andrey Pohilko <[hidden email]> wrote:
Hi,

I'm the maintainer for performance-plugin repo.

I'm trying to use my typical approach with controlling the project quality using GitHub+TravisCI+Codecov integration, which proven its value for me. However, I'm missing the admin right on repo to enable TravisCI for it. Can anybody help me enabling it? I don't need the admin rights per se, just need to enable TravisCI for it.

https://travis-ci.org/jenkinsci/performance-plugin

--
Andrey

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/d43f9a06-568c-4d29-995f-e182f093a703%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to a topic in the Google Groups "Jenkins Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-dev/n3b2LbHeV6Y/unsubscribe.
To unsubscribe from this group and all its topics, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAN4CQ4xaX%2BMp8es0%3DdkR01ychfL1JTxinPj%2BA0BYLpD5hnWOBQ%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/A0AE4D84-52CC-497C-AF71-2D8389FC921D%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAN4CQ4yC7BHGC6frQMY_aE_Nt3c8FTMyLioHwMyYJLE6X3TOGQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: How to enable Travis CI for jenkins plugin repo

Kanstantsin Shautsou-2

On Jul 21, 2016, at 02:14, Kohsuke Kawaguchi <[hidden email]> wrote:

Jenkins does provide a way to configure the build process, for example via Jenkinsfile, via Job DSL plugin, etc.
Thanks, i know.

Like I said in my previous email, it's just that in jenkins.io.cloudbees.com we choose to use a template to lock things down.
That what i mean.

IIUC reviewable.io is orthogonal to this. That's between GitHub and it.
It requires admin access in repo to setup hooks.


On Wed, Jul 20, 2016 at 1:55 PM Kanstantsin Shautsou <[hidden email]> wrote:
Jenkins CloudBees doesn’t provide any ways to control or configure build process and integrations. In 2016 that’s blocker for development. Also you can’t do anything with reviewable.io because you have no analogues.

On Jul 20, 2016, at 23:51, Kohsuke Kawaguchi <[hidden email]> wrote:

So in this case the motivation is to activate Codecov.io on plugins. On https://jenkins.ci.cloudbees.com/job/plugins/ we use templating so that we only need to change the setting once to impact every plugin.

If we make that change across the board, would that make you happy enough to stop the use of Travis? It seems like it's a relatively easy change to make it happen, and I think it'd benefit everyone.

I'm asking because I think it sends a wrong signal when we are using Travis for something Jenkins does just as well.

On Wed, Jul 6, 2016 at 2:12 AM Andrey Pohilko <[hidden email]> wrote:
Hi,

I'm the maintainer for performance-plugin repo.

I'm trying to use my typical approach with controlling the project quality using GitHub+TravisCI+Codecov integration, which proven its value for me. However, I'm missing the admin right on repo to enable TravisCI for it. Can anybody help me enabling it? I don't need the admin rights per se, just need to enable TravisCI for it.

https://travis-ci.org/jenkinsci/performance-plugin

--
Andrey

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/d43f9a06-568c-4d29-995f-e182f093a703%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to a topic in the Google Groups "Jenkins Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-dev/n3b2LbHeV6Y/unsubscribe.
To unsubscribe from this group and all its topics, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAN4CQ4xaX%2BMp8es0%3DdkR01ychfL1JTxinPj%2BA0BYLpD5hnWOBQ%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/A0AE4D84-52CC-497C-AF71-2D8389FC921D%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to a topic in the Google Groups "Jenkins Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-dev/n3b2LbHeV6Y/unsubscribe.
To unsubscribe from this group and all its topics, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAN4CQ4yC7BHGC6frQMY_aE_Nt3c8FTMyLioHwMyYJLE6X3TOGQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/167C3B70-E522-4230-8FEC-2C0C36BC9348%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

signature.asc (859 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: How to enable Travis CI for jenkins plugin repo

Gavin Mogan
In reply to this post by Kohsuke Kawaguchi
I asked the same question late last year.

I have heard rumors that the cloudbees templates are being updated to use Jenkinsfile, which would be awesome.

Right now we've forked and done development on our own repo so we can trigger a build that does codecov and a few other minor things, but it would be amazing to use jenkins full time and be able to provide secure credentials somewhow.

Short term though, I'd love codecov ('cause thats what I'm using too)

Gavin

On Wednesday, July 20, 2016 at 1:51:14 PM UTC-7, Kohsuke Kawaguchi wrote:
So in this case the motivation is to activate Codecov.io on plugins. On <a href="https://jenkins.ci.cloudbees.com/job/plugins/" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fjenkins.ci.cloudbees.com%2Fjob%2Fplugins%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHzfM3Ju2RgYDN4ZKgEfbgJfo4bwA&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fjenkins.ci.cloudbees.com%2Fjob%2Fplugins%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHzfM3Ju2RgYDN4ZKgEfbgJfo4bwA&#39;;return true;">https://jenkins.ci.cloudbees.com/job/plugins/ we use templating so that we only need to change the setting once to impact every plugin.

If we make that change across the board, would that make you happy enough to stop the use of Travis? It seems like it's a relatively easy change to make it happen, and I think it'd benefit everyone.

I'm asking because I think it sends a wrong signal when we are using Travis for something Jenkins does just as well.

On Wed, Jul 6, 2016 at 2:12 AM Andrey Pohilko <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="mXhgoLMKAgAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">ap...@...> wrote:
Hi,

I'm the maintainer for performance-plugin repo.

I'm trying to use my typical approach with controlling the project quality using GitHub+TravisCI+Codecov integration, which proven its value for me. However, I'm missing the admin right on repo to enable TravisCI for it. Can anybody help me enabling it? I don't need the admin rights per se, just need to enable TravisCI for it.

<a href="https://travis-ci.org/jenkinsci/performance-plugin" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Ftravis-ci.org%2Fjenkinsci%2Fperformance-plugin\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHLPhYEm90yuueoPSz43BdGIkfutQ&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Ftravis-ci.org%2Fjenkinsci%2Fperformance-plugin\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHLPhYEm90yuueoPSz43BdGIkfutQ&#39;;return true;">https://travis-ci.org/jenkinsci/performance-plugin

--
Andrey

--
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 <a href="javascript:" target="_blank" gdf-obfuscated-mailto="mXhgoLMKAgAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/jenkinsci-dev/d43f9a06-568c-4d29-995f-e182f093a703%40googlegroups.com?utm_medium=email&amp;utm_source=footer" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/d43f9a06-568c-4d29-995f-e182f093a703%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/d43f9a06-568c-4d29-995f-e182f093a703%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;">https://groups.google.com/d/msgid/jenkinsci-dev/d43f9a06-568c-4d29-995f-e182f093a703%40googlegroups.com.
For more options, visit <a href="https://groups.google.com/d/optout" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;">https://groups.google.com/d/optout.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/2a7e33bc-c9cf-403c-8e8c-a9eb53629bac%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: How to enable Travis CI for jenkins plugin repo

Arnaud Héritier
codecov is a competitor of SonarQube ?

On Thu, Jul 21, 2016 at 8:18 PM, Gavin Mogan <[hidden email]> wrote:
I asked the same question late last year.

I have heard rumors that the cloudbees templates are being updated to use Jenkinsfile, which would be awesome.

Right now we've forked and done development on our own repo so we can trigger a build that does codecov and a few other minor things, but it would be amazing to use jenkins full time and be able to provide secure credentials somewhow.

Short term though, I'd love codecov ('cause thats what I'm using too)

Gavin

On Wednesday, July 20, 2016 at 1:51:14 PM UTC-7, Kohsuke Kawaguchi wrote:
So in this case the motivation is to activate Codecov.io on plugins. On https://jenkins.ci.cloudbees.com/job/plugins/ we use templating so that we only need to change the setting once to impact every plugin.

If we make that change across the board, would that make you happy enough to stop the use of Travis? It seems like it's a relatively easy change to make it happen, and I think it'd benefit everyone.

I'm asking because I think it sends a wrong signal when we are using Travis for something Jenkins does just as well.

On Wed, Jul 6, 2016 at 2:12 AM Andrey Pohilko <[hidden email]> wrote:
Hi,

I'm the maintainer for performance-plugin repo.

I'm trying to use my typical approach with controlling the project quality using GitHub+TravisCI+Codecov integration, which proven its value for me. However, I'm missing the admin right on repo to enable TravisCI for it. Can anybody help me enabling it? I don't need the admin rights per se, just need to enable TravisCI for it.

https://travis-ci.org/jenkinsci/performance-plugin

--
Andrey

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/d43f9a06-568c-4d29-995f-e182f093a703%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/2a7e33bc-c9cf-403c-8e8c-a9eb53629bac%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.



--
-----
Arnaud Héritier
Mail/GTalk: aheritier AT gmail DOT com
Twitter/Skype : aheritier

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAFNCU-8eTg0T9DYVvsEVBtLrBTA0_-acL4b%3DLhAZE3RUHt60eA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: How to enable Travis CI for jenkins plugin repo

Kanstantsin Shautsou-2
Good question, AFAIR we discussed few times to have SonarQube and Coverity specially for Jenkins, but end with unability to do something in INFRA.
According to email answer, public sonarqube (nemo instance?) has no “service” feature where people can manage themselves configuration. 
Codecov.io is only about coverage based on jacoco results (sonar seems is more powerful, but missing stats per branche).

Pushing automatically from jenkinsci will work. Jenkinsfile should work for custom envs, but what could be done with env internals is under question. With travis it is possible to run any SW/daemons internally. Ans is Jenkinsfile already available for plugins?

On Jul 21, 2016, at 22:52, Arnaud Héritier <[hidden email]> wrote:

codecov is a competitor of SonarQube ?

On Thu, Jul 21, 2016 at 8:18 PM, Gavin Mogan <[hidden email]> wrote:
I asked the same question late last year.

I have heard rumors that the cloudbees templates are being updated to use Jenkinsfile, which would be awesome.

Right now we've forked and done development on our own repo so we can trigger a build that does codecov and a few other minor things, but it would be amazing to use jenkins full time and be able to provide secure credentials somewhow.

Short term though, I'd love codecov ('cause thats what I'm using too)

Gavin

On Wednesday, July 20, 2016 at 1:51:14 PM UTC-7, Kohsuke Kawaguchi wrote:
So in this case the motivation is to activate Codecov.io on plugins. On https://jenkins.ci.cloudbees.com/job/plugins/ we use templating so that we only need to change the setting once to impact every plugin.

If we make that change across the board, would that make you happy enough to stop the use of Travis? It seems like it's a relatively easy change to make it happen, and I think it'd benefit everyone.

I'm asking because I think it sends a wrong signal when we are using Travis for something Jenkins does just as well.

On Wed, Jul 6, 2016 at 2:12 AM Andrey Pohilko <[hidden email]> wrote:
Hi,

I'm the maintainer for performance-plugin repo.

I'm trying to use my typical approach with controlling the project quality using GitHub+TravisCI+Codecov integration, which proven its value for me. However, I'm missing the admin right on repo to enable TravisCI for it. Can anybody help me enabling it? I don't need the admin rights per se, just need to enable TravisCI for it.

https://travis-ci.org/jenkinsci/performance-plugin

--
Andrey

-- 
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/d43f9a06-568c-4d29-995f-e182f093a703%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

-- 
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/2a7e33bc-c9cf-403c-8e8c-a9eb53629bac%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.



-- 
-----
Arnaud Héritier
Mail/GTalk: aheritier AT gmail DOT com
Twitter/Skype : aheritier

-- 
You received this message because you are subscribed to a topic in the Google Groups "Jenkins Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-dev/n3b2LbHeV6Y/unsubscribe.
To unsubscribe from this group and all its topics, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAFNCU-8eTg0T9DYVvsEVBtLrBTA0_-acL4b%3DLhAZE3RUHt60eA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/66CF2B31-3921-4888-9B00-CA7BBE0B4C3A%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

signature.asc (859 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: How to enable Travis CI for jenkins plugin repo

Thomas Zoratto
I’m not sure if this is what you mean by 'missing stats per branche' or not but you can have different reports for each branch in SonarQube (see sonar.branch property http://docs.sonarqube.org/display/SONAR/Analysis+Parameters)

Le 22 juil. 2016 à 00:27, Kanstantsin Shautsou <[hidden email]> a écrit :

Good question, AFAIR we discussed few times to have SonarQube and Coverity specially for Jenkins, but end with unability to do something in INFRA.
According to email answer, public sonarqube (nemo instance?) has no “service” feature where people can manage themselves configuration. 
Codecov.io is only about coverage based on jacoco results (sonar seems is more powerful, but missing stats per branche).

Pushing automatically from jenkinsci will work. Jenkinsfile should work for custom envs, but what could be done with env internals is under question. With travis it is possible to run any SW/daemons internally. Ans is Jenkinsfile already available for plugins?

On Jul 21, 2016, at 22:52, Arnaud Héritier <[hidden email]> wrote:

codecov is a competitor of SonarQube ?

On Thu, Jul 21, 2016 at 8:18 PM, Gavin Mogan <[hidden email]> wrote:
I asked the same question late last year.

I have heard rumors that the cloudbees templates are being updated to use Jenkinsfile, which would be awesome.

Right now we've forked and done development on our own repo so we can trigger a build that does codecov and a few other minor things, but it would be amazing to use jenkins full time and be able to provide secure credentials somewhow.

Short term though, I'd love codecov ('cause thats what I'm using too)

Gavin

On Wednesday, July 20, 2016 at 1:51:14 PM UTC-7, Kohsuke Kawaguchi wrote:
So in this case the motivation is to activate Codecov.io on plugins. On https://jenkins.ci.cloudbees.com/job/plugins/ we use templating so that we only need to change the setting once to impact every plugin.

If we make that change across the board, would that make you happy enough to stop the use of Travis? It seems like it's a relatively easy change to make it happen, and I think it'd benefit everyone.

I'm asking because I think it sends a wrong signal when we are using Travis for something Jenkins does just as well.

On Wed, Jul 6, 2016 at 2:12 AM Andrey Pohilko <[hidden email]> wrote:
Hi,

I'm the maintainer for performance-plugin repo.

I'm trying to use my typical approach with controlling the project quality using GitHub+TravisCI+Codecov integration, which proven its value for me. However, I'm missing the admin right on repo to enable TravisCI for it. Can anybody help me enabling it? I don't need the admin rights per se, just need to enable TravisCI for it.

https://travis-ci.org/jenkinsci/performance-plugin

--
Andrey

-- 
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/d43f9a06-568c-4d29-995f-e182f093a703%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

-- 
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/2a7e33bc-c9cf-403c-8e8c-a9eb53629bac%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.



-- 
-----
Arnaud Héritier
Mail/GTalk: aheritier AT gmail DOT com
Twitter/Skype : aheritier

-- 
You received this message because you are subscribed to a topic in the Google Groups "Jenkins Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-dev/n3b2LbHeV6Y/unsubscribe.
To unsubscribe from this group and all its topics, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAFNCU-8eTg0T9DYVvsEVBtLrBTA0_-acL4b%3DLhAZE3RUHt60eA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/66CF2B31-3921-4888-9B00-CA7BBE0B4C3A%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/18D13E5D-9A9C-431D-B145-56C712F14446%40gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: How to enable Travis CI for jenkins plugin repo

Kanstantsin Shautsou-2
Thanks, will look. Doc appeared one week ago?

On Friday, July 22, 2016 at 2:46:44 PM UTC+3, Thomas Zoratto wrote:
I’m not sure if this is what you mean by 'missing stats per branche' or not but you can have different reports for each branch in SonarQube (see sonar.branch property <a href="http://docs.sonarqube.org/display/SONAR/Analysis+Parameters" target="_blank" rel="nofollow" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fdocs.sonarqube.org%2Fdisplay%2FSONAR%2FAnalysis%2BParameters\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFjQU-rca4LMomBbFavb4m5gaSJ3Q&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fdocs.sonarqube.org%2Fdisplay%2FSONAR%2FAnalysis%2BParameters\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFjQU-rca4LMomBbFavb4m5gaSJ3Q&#39;;return true;">http://docs.sonarqube.org/display/SONAR/Analysis+Parameters)

Le 22 juil. 2016 à 00:27, Kanstantsin Shautsou <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="zGlbGSaKAgAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">kanstan...@...> a écrit :

Good question, AFAIR we discussed few times to have SonarQube and Coverity specially for Jenkins, but end with unability to do something in INFRA.
According to email answer, public sonarqube (nemo instance?) has no “service” feature where people can manage themselves configuration. 
<a href="http://codecov.io/" target="_blank" rel="nofollow" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fcodecov.io%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGR8KhV-65pdfAjExhtM_2RUJnXzw&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fcodecov.io%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGR8KhV-65pdfAjExhtM_2RUJnXzw&#39;;return true;">Codecov.io is only about coverage based on jacoco results (sonar seems is more powerful, but missing stats per branche).

Pushing automatically from jenkinsci will work. Jenkinsfile should work for custom envs, but what could be done with env internals is under question. With travis it is possible to run any SW/daemons internally. Ans is Jenkinsfile already available for plugins?

On Jul 21, 2016, at 22:52, Arnaud Héritier <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="zGlbGSaKAgAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">aher...@...> wrote:

codecov is a competitor of SonarQube ?

ex : <a href="https://sonarqube.com/overview?id=org.jenkins-ci.main:pom" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fsonarqube.com%2Foverview%3Fid%3Dorg.jenkins-ci.main%3Apom\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFUrE6-tnHHTLlUfb5195wobQ255g&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fsonarqube.com%2Foverview%3Fid%3Dorg.jenkins-ci.main%3Apom\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFUrE6-tnHHTLlUfb5195wobQ255g&#39;;return true;">https://sonarqube.com/overview?id=org.jenkins-ci.main%3Apom

On Thu, Jul 21, 2016 at 8:18 PM, Gavin Mogan <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="zGlbGSaKAgAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">ga...@...> wrote:
I asked the same question late last year.

I have heard rumors that the cloudbees templates are being updated to use Jenkinsfile, which would be awesome.

Right now we've forked and done development on our own repo so we can trigger a build that does codecov and a few other minor things, but it would be amazing to use jenkins full time and be able to provide secure credentials somewhow.

Short term though, I'd love codecov ('cause thats what I'm using too)

Gavin

On Wednesday, July 20, 2016 at 1:51:14 PM UTC-7, Kohsuke Kawaguchi wrote:
So in this case the motivation is to activate <a href="http://codecov.io/" target="_blank" rel="nofollow" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fcodecov.io%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGR8KhV-65pdfAjExhtM_2RUJnXzw&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fcodecov.io%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGR8KhV-65pdfAjExhtM_2RUJnXzw&#39;;return true;">Codecov.io on plugins. On <a href="https://jenkins.ci.cloudbees.com/job/plugins/" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fjenkins.ci.cloudbees.com%2Fjob%2Fplugins%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHzfM3Ju2RgYDN4ZKgEfbgJfo4bwA&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fjenkins.ci.cloudbees.com%2Fjob%2Fplugins%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHzfM3Ju2RgYDN4ZKgEfbgJfo4bwA&#39;;return true;">https://jenkins.ci.cloudbees.com/job/plugins/ we use templating so that we only need to change the setting once to impact every plugin.

If we make that change across the board, would that make you happy enough to stop the use of Travis? It seems like it's a relatively easy change to make it happen, and I think it'd benefit everyone.

I'm asking because I think it sends a wrong signal when we are using Travis for something Jenkins does just as well.

On Wed, Jul 6, 2016 at 2:12 AM Andrey Pohilko <[hidden email]> wrote:
Hi,

I'm the maintainer for performance-plugin repo.

I'm trying to use my typical approach with controlling the project quality using GitHub+TravisCI+Codecov integration, which proven its value for me. However, I'm missing the admin right on repo to enable TravisCI for it. Can anybody help me enabling it? I don't need the admin rights per se, just need to enable TravisCI for it.

<a href="https://travis-ci.org/jenkinsci/performance-plugin" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Ftravis-ci.org%2Fjenkinsci%2Fperformance-plugin\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHLPhYEm90yuueoPSz43BdGIkfutQ&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Ftravis-ci.org%2Fjenkinsci%2Fperformance-plugin\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHLPhYEm90yuueoPSz43BdGIkfutQ&#39;;return true;">https://travis-ci.org/jenkinsci/performance-plugin

--
Andrey

-- 
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-de...@googlegroups.com.
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/jenkinsci-dev/d43f9a06-568c-4d29-995f-e182f093a703%40googlegroups.com?utm_medium=email&amp;utm_source=footer" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/d43f9a06-568c-4d29-995f-e182f093a703%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/d43f9a06-568c-4d29-995f-e182f093a703%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;">https://groups.google.com/d/msgid/jenkinsci-dev/d43f9a06-568c-4d29-995f-e182f093a703%40googlegroups.com.
For more options, visit <a href="https://groups.google.com/d/optout" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;">https://groups.google.com/d/optout.

-- 
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 <a href="javascript:" target="_blank" gdf-obfuscated-mailto="zGlbGSaKAgAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/jenkinsci-dev/2a7e33bc-c9cf-403c-8e8c-a9eb53629bac%40googlegroups.com?utm_medium=email&amp;utm_source=footer" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/2a7e33bc-c9cf-403c-8e8c-a9eb53629bac%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/2a7e33bc-c9cf-403c-8e8c-a9eb53629bac%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;">https://groups.google.com/d/msgid/jenkinsci-dev/2a7e33bc-c9cf-403c-8e8c-a9eb53629bac%40googlegroups.com.

For more options, visit <a href="https://groups.google.com/d/optout" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;">https://groups.google.com/d/optout.



-- 
-----
Arnaud Héritier
<a href="http://aheritier.net/" target="_blank" rel="nofollow" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Faheritier.net%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNERIIhY4USdeq-5u8v-KusriQLDxw&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Faheritier.net%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNERIIhY4USdeq-5u8v-KusriQLDxw&#39;;return true;">http://aheritier.net
Mail/GTalk: aheritier AT gmail DOT com
Twitter/Skype : aheritier

-- 
You received this message because you are subscribed to a topic in the Google Groups "Jenkins Developers" group.
To unsubscribe from this topic, visit <a href="https://groups.google.com/d/topic/jenkinsci-dev/n3b2LbHeV6Y/unsubscribe" style="font-family:Helvetica;font-size:12px;font-style:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/topic/jenkinsci-dev/n3b2LbHeV6Y/unsubscribe&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/topic/jenkinsci-dev/n3b2LbHeV6Y/unsubscribe&#39;;return true;">https://groups.google.com/d/topic/jenkinsci-dev/n3b2LbHeV6Y/unsubscribe.
To unsubscribe from this group and all its topics, send an email to <a href="javascript:" style="font-family:Helvetica;font-size:12px;font-style:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px" target="_blank" gdf-obfuscated-mailto="zGlbGSaKAgAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/jenkinsci-dev/CAFNCU-8eTg0T9DYVvsEVBtLrBTA0_-acL4b%3DLhAZE3RUHt60eA%40mail.gmail.com?utm_medium=email&amp;utm_source=footer" style="font-family:Helvetica;font-size:12px;font-style:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/CAFNCU-8eTg0T9DYVvsEVBtLrBTA0_-acL4b%3DLhAZE3RUHt60eA%40mail.gmail.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/CAFNCU-8eTg0T9DYVvsEVBtLrBTA0_-acL4b%3DLhAZE3RUHt60eA%40mail.gmail.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;">https://groups.google.com/d/msgid/jenkinsci-dev/CAFNCU-8eTg0T9DYVvsEVBtLrBTA0_-acL4b%3DLhAZE3RUHt60eA%40mail.gmail.com.
For more options, visit <a href="https://groups.google.com/d/optout" style="font-family:Helvetica;font-size:12px;font-style:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;">https://groups.google.com/d/optout.


--
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 <a href="javascript:" target="_blank" gdf-obfuscated-mailto="zGlbGSaKAgAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/jenkinsci-dev/66CF2B31-3921-4888-9B00-CA7BBE0B4C3A%40gmail.com?utm_medium=email&amp;utm_source=footer" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/66CF2B31-3921-4888-9B00-CA7BBE0B4C3A%40gmail.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/66CF2B31-3921-4888-9B00-CA7BBE0B4C3A%40gmail.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;">https://groups.google.com/d/msgid/jenkinsci-dev/66CF2B31-3921-4888-9B00-CA7BBE0B4C3A%40gmail.com.
For more options, visit <a href="https://groups.google.com/d/optout" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;">https://groups.google.com/d/optout.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/b94d79fb-423f-4a9c-97d2-cf8edf9e7040%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: How to enable Travis CI for jenkins plugin repo

Arnaud Héritier
I think it exists for a long time, I used it in my previous company to manage quality indicators accross several development baselines/branches


On Fri, Jul 22, 2016 at 4:54 PM, Kanstantsin Shautsou <[hidden email]> wrote:
Thanks, will look. Doc appeared one week ago?

On Friday, July 22, 2016 at 2:46:44 PM UTC+3, Thomas Zoratto wrote:
I’m not sure if this is what you mean by 'missing stats per branche' or not but you can have different reports for each branch in SonarQube (see sonar.branch property http://docs.sonarqube.org/display/SONAR/Analysis+Parameters)

Le 22 juil. 2016 à 00:27, Kanstantsin Shautsou <[hidden email]> a écrit :

Good question, AFAIR we discussed few times to have SonarQube and Coverity specially for Jenkins, but end with unability to do something in INFRA.
According to email answer, public sonarqube (nemo instance?) has no “service” feature where people can manage themselves configuration. 
Codecov.io is only about coverage based on jacoco results (sonar seems is more powerful, but missing stats per branche).

Pushing automatically from jenkinsci will work. Jenkinsfile should work for custom envs, but what could be done with env internals is under question. With travis it is possible to run any SW/daemons internally. Ans is Jenkinsfile already available for plugins?

On Jul 21, 2016, at 22:52, Arnaud Héritier <[hidden email]> wrote:

codecov is a competitor of SonarQube ?

On Thu, Jul 21, 2016 at 8:18 PM, Gavin Mogan <[hidden email]> wrote:
I asked the same question late last year.

I have heard rumors that the cloudbees templates are being updated to use Jenkinsfile, which would be awesome.

Right now we've forked and done development on our own repo so we can trigger a build that does codecov and a few other minor things, but it would be amazing to use jenkins full time and be able to provide secure credentials somewhow.

Short term though, I'd love codecov ('cause thats what I'm using too)

Gavin

On Wednesday, July 20, 2016 at 1:51:14 PM UTC-7, Kohsuke Kawaguchi wrote:
So in this case the motivation is to activate Codecov.io on plugins. On https://jenkins.ci.cloudbees.com/job/plugins/ we use templating so that we only need to change the setting once to impact every plugin.

If we make that change across the board, would that make you happy enough to stop the use of Travis? It seems like it's a relatively easy change to make it happen, and I think it'd benefit everyone.

I'm asking because I think it sends a wrong signal when we are using Travis for something Jenkins does just as well.

On Wed, Jul 6, 2016 at 2:12 AM Andrey Pohilko <[hidden email]> wrote:
Hi,

I'm the maintainer for performance-plugin repo.

I'm trying to use my typical approach with controlling the project quality using GitHub+TravisCI+Codecov integration, which proven its value for me. However, I'm missing the admin right on repo to enable TravisCI for it. Can anybody help me enabling it? I don't need the admin rights per se, just need to enable TravisCI for it.

https://travis-ci.org/jenkinsci/performance-plugin

--
Andrey

-- 
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/d43f9a06-568c-4d29-995f-e182f093a703%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

-- 
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/2a7e33bc-c9cf-403c-8e8c-a9eb53629bac%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.



-- 
-----
Arnaud Héritier
Mail/GTalk: aheritier AT gmail DOT com
Twitter/Skype : aheritier

-- 
You received this message because you are subscribed to a topic in the Google Groups "Jenkins Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-dev/n3b2LbHeV6Y/unsubscribe.
To unsubscribe from this group and all its topics, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAFNCU-8eTg0T9DYVvsEVBtLrBTA0_-acL4b%3DLhAZE3RUHt60eA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/66CF2B31-3921-4888-9B00-CA7BBE0B4C3A%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/b94d79fb-423f-4a9c-97d2-cf8edf9e7040%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.



--
-----
Arnaud Héritier
Mail/GTalk: aheritier AT gmail DOT com
Twitter/Skype : aheritier

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAFNCU-_QT1cfxpv2n3k6cchDTVVz0rvOTNHNksBeA6BQPngYCA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: How to enable Travis CI for jenkins plugin repo

Thomas Zoratto
In reply to this post by Kanstantsin Shautsou-2
The doc was only updated one week ago.

As Arnaud pointed out, this property is available for a long time I think. You can find a reference about it in a old 2009 article (http://www.sonarqube.org/using-quality-profiles-in-sonar/)

Le 22 juil. 2016 à 16:54, Kanstantsin Shautsou <[hidden email]> a écrit :


--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/49CDC5E5-9DC6-45EE-9F92-EA8DDC29A75B%40gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: How to enable Travis CI for jenkins plugin repo

Baptiste MATHUS

Yup +1. I can relate. This property has been existing for years and we used it quite a lot.

Cheers


Le 22 juil. 2016 6:24 PM, "Thomas Zoratto" <[hidden email]> a écrit :
The doc was only updated one week ago.

As Arnaud pointed out, this property is available for a long time I think. You can find a reference about it in a old 2009 article (http://www.sonarqube.org/using-quality-profiles-in-sonar/)

Le 22 juil. 2016 à 16:54, Kanstantsin Shautsou <[hidden email]> a écrit :


--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/49CDC5E5-9DC6-45EE-9F92-EA8DDC29A75B%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS6S-0YJ1Gz8grVvtUwrzvrQv0wJpXmh-cTNK8MvRkXUog%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: How to enable Travis CI for jenkins plugin repo

Craig Rodrigues
In reply to this post by Kohsuke Kawaguchi
I'm OK with Cloudbees using a template to lock things down for jenkins.io.cloudbees.com.

One thing I would suggest is that in JIRA, if someone files an issue at https://issues.jenkins-ci.org
in Project Infrastructure, Component: ci, instead of auto-assigning the issue to one
person (rtyler), it goes to a team of people who can maintain this.

For example, I filed https://issues.jenkins-ci.org/browse/INFRA-741 in June, and that got punted to Andrew Bayer.
Andrew is super-busy doing dev work on Jenkins, so I'm glad he has helped in the past, but I don't
think this kind of stuff should get assigned to him, because his considerable brainpower is better spent
on other activities, IMHO.

Regarding Travis, it is an excellent service, and I use it heavily for some other projects I am involved in.
I have also used Appveyor and Codecov.io, and they are also excellent services.

Travis and Appveyor are slightly competing with Jenkins, so I think it is understandable for Cloudbees to want to
favor Jenkins for doing CI rather than using third party products and services.  It doesn't look good, otherwise.

However, the Jenkins project and Cloudbees should see what can be done to improve the level of support,
and also the feature set of jenkins.io.cloudbees.com, so that users do not even have to consider using Travis
for Jenkins plugins.

On a side note, I hope that the Plumber plugin work that Andrew has been working on goes farther along.
Andrew gave me a demo of a YAML based configuration of a  pipeline workflow.  I was impressed.  This is very close
to the YAML configurations that Travis and Appveyor offer.

--
Craig


On Wed, Jul 20, 2016 at 4:14 PM, Kohsuke Kawaguchi <[hidden email]> wrote:

Like I said in my previous email, it's just that in jenkins.io.cloudbees.com we choose to use a template to lock things down.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3DrPVeNHKKoRT-9Mv%3DJY41D%2BNWa%3DEogXQiS7n358C1fNNN%3DXg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: How to enable Travis CI for jenkins plugin repo

Arnaud Héritier
INFRA-741 fixed. But I agree that it is better to not assign them.
Also our community CI should evolve soon with our recent partnership with Azure : https://jenkins.io/blog/2016/05/18/announcing-azure-partnership/

On Thu, Aug 4, 2016 at 9:15 AM, Craig Rodrigues <[hidden email]> wrote:
I'm OK with Cloudbees using a template to lock things down for jenkins.io.cloudbees.com.

One thing I would suggest is that in JIRA, if someone files an issue at https://issues.jenkins-ci.org
in Project Infrastructure, Component: ci, instead of auto-assigning the issue to one
person (rtyler), it goes to a team of people who can maintain this.

For example, I filed https://issues.jenkins-ci.org/browse/INFRA-741 in June, and that got punted to Andrew Bayer.
Andrew is super-busy doing dev work on Jenkins, so I'm glad he has helped in the past, but I don't
think this kind of stuff should get assigned to him, because his considerable brainpower is better spent
on other activities, IMHO.

Regarding Travis, it is an excellent service, and I use it heavily for some other projects I am involved in.
I have also used Appveyor and Codecov.io, and they are also excellent services.

Travis and Appveyor are slightly competing with Jenkins, so I think it is understandable for Cloudbees to want to
favor Jenkins for doing CI rather than using third party products and services.  It doesn't look good, otherwise.

However, the Jenkins project and Cloudbees should see what can be done to improve the level of support,
and also the feature set of jenkins.io.cloudbees.com, so that users do not even have to consider using Travis
for Jenkins plugins.

On a side note, I hope that the Plumber plugin work that Andrew has been working on goes farther along.
Andrew gave me a demo of a YAML based configuration of a  pipeline workflow.  I was impressed.  This is very close
to the YAML configurations that Travis and Appveyor offer.

--
Craig


On Wed, Jul 20, 2016 at 4:14 PM, Kohsuke Kawaguchi <[hidden email]> wrote:

Like I said in my previous email, it's just that in jenkins.io.cloudbees.com we choose to use a template to lock things down.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3DrPVeNHKKoRT-9Mv%3DJY41D%2BNWa%3DEogXQiS7n358C1fNNN%3DXg%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.



--
-----
Arnaud Héritier
Mail/GTalk: aheritier AT gmail DOT com
Twitter/Skype : aheritier

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAFNCU-9vBC6y28pZODjgDLcQWW_tD7pQmfTqp%3Dd7h8pYZ5keLw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: How to enable Travis CI for jenkins plugin repo

Craig Rodrigues
Arnaud,

Thanks for fixing this.  How can I put a proposal to the Jenkins admins
that if a ticket is filed with Project Infrastructure, Component CI that
it gets assigned to a group of people, and not a single person?

I'm not able to attend the weekly Jenkins governance meetings.

Due to the popularity of Jenkins and the high volume of e-mails,
the Jenkins mailing lists are increasingly becoming hard to follow
and unusable for tracking the status of requests.

Thanks.
--
Craig


On Thu, Aug 4, 2016 at 12:40 AM, Arnaud Héritier <[hidden email]> wrote:
INFRA-741 fixed. But I agree that it is better to not assign them.
Also our community CI should evolve soon with our recent partnership with Azure : https://jenkins.io/blog/2016/05/18/announcing-azure-partnership/

On Thu, Aug 4, 2016 at 9:15 AM, Craig Rodrigues <[hidden email]> wrote:
I'm OK with Cloudbees using a template to lock things down for jenkins.io.cloudbees.com.

One thing I would suggest is that in JIRA, if someone files an issue at https://issues.jenkins-ci.org
in Project Infrastructure, Component: ci, instead of auto-assigning the issue to one
person (rtyler), it goes to a team of people who can maintain this.

For example, I filed https://issues.jenkins-ci.org/browse/INFRA-741 in June, and that got punted to Andrew Bayer.
Andrew is super-busy doing dev work on Jenkins, so I'm glad he has helped in the past, but I don't
think this kind of stuff should get assigned to him, because his considerable brainpower is better spent
on other activities, IMHO.

Regarding Travis, it is an excellent service, and I use it heavily for some other projects I am involved in.
I have also used Appveyor and Codecov.io, and they are also excellent services.

Travis and Appveyor are slightly competing with Jenkins, so I think it is understandable for Cloudbees to want to
favor Jenkins for doing CI rather than using third party products and services.  It doesn't look good, otherwise.

However, the Jenkins project and Cloudbees should see what can be done to improve the level of support,
and also the feature set of jenkins.io.cloudbees.com, so that users do not even have to consider using Travis
for Jenkins plugins.

On a side note, I hope that the Plumber plugin work that Andrew has been working on goes farther along.
Andrew gave me a demo of a YAML based configuration of a  pipeline workflow.  I was impressed.  This is very close
to the YAML configurations that Travis and Appveyor offer.

--
Craig


On Wed, Jul 20, 2016 at 4:14 PM, Kohsuke Kawaguchi <[hidden email]> wrote:

Like I said in my previous email, it's just that in jenkins.io.cloudbees.com we choose to use a template to lock things down.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3DrPVeNHKKoRT-9Mv%3DJY41D%2BNWa%3DEogXQiS7n358C1fNNN%3DXg%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.



--
-----
Arnaud Héritier
Mail/GTalk: aheritier AT gmail DOT com
Twitter/Skype : aheritier

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAFNCU-9vBC6y28pZODjgDLcQWW_tD7pQmfTqp%3Dd7h8pYZ5keLw%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3DrPVc5LtcMsHzDFu8p4mug%3DkXQ17zt9HfSjhHcA1SpsS6_6Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
12
Loading...