Re: Own Cloud Plugin: "ClassNotFoundException: javax.servlet.ServletException" when running job for the first time

[Baptiste Mathus]

Note that the Incrementals repo is *not* configured behind
http://repo.jenkins-ci.org/public/ group repo on purpose.
So to enable automatic addition of that repository, you must add
-Pconsume-incrementals to your command line call, and hence use a recent
parent pom. See https://github.com/jenkinsci/plugin-pom

I think some ~3.18+ should be enough, but I'd recommend updating to latest
3.28 or 3.29 to avoid issues.

Le mer. 5 déc. 2018 à 21:23, Daniel Beck  a écrit :

>
>
> > On 5. Dec 2018, at 18:01, Johannes Schneider 
> wrote:
> >
> > which does not work (of course) because I don't have a snapshot
> repository configured. A quick search didn't give me
> > the the URL for the snapshot repository. Could you help me out?
> >
>
> Incrementals are deployed to https://repo.jenkins-ci.org/incrementals/
>
> --
> 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/A3911619-D4B1-4672-9974-151BC497538F%40beckweb.net
> .
> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS5dtBwShE22sVnE3dhJO3DUTebBrZehw5xm82%3DZX1FJxg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Java 11 Preview availability in Weekly releases. Status update (JEP-211)

[Oleg Nenashev]

Dear all,

I would like to briefly summarize the status of the ongoing Java 11 support
effort in the Jenkins project. Java 11 has been released on Sep 25, and
this is an LTS Java version which will stay around for many years. In the
Jenkins project we are interested to support this version, and there has
been a good progress since we have started this effort in June 2018. There
is a JEP-211 
document describing the process.

Today we have discussed the rollout plan at the Governance meeting, and our
I would like to start a thread before the tomorrow's Platform SIG
 meeting. Our current goal is the
Preview Availability in Jenkins weekly releases (EPIC - JENKINS-52012
), and I think we could
announce such availability* on the next week*. The goal of this milestone
is to announce Java 11 support preview among Jenkins contributors, plugin
maintainers and early adopters. It is not a general availability, and Java
11 will stay protected by a feature flag for now. See the Rollout Plan
 for
details.

*Current status*

   - By Nov 19 2018 we have integrated all Jenkins core patches we planned
   for the preview availability. The results were presented at the Platform
   SIG meeting (meeting notes
   
,
   status update slides
   

   )
   - All major patches have been integrated into Jenkins Jenkins 2.145, so
   technically it is possible to run the current LTS with Java 11 if you pass
   the feature flag and libraries properly (old guidelines
   
   )
   - We have started a Wiki page
   
   for known compatibility issues. Thanks Baptiste!
   - At that call on Nov 19 we identified 3 main blockers for the preview
   availability, see below
   - *Blocker 1. Pipeline: Support plugin* release with Java 11
   compatibility patches (JENKINS-52187
   )
  - The final patch is in progress (thanks Sam), but we plan to deploy
  a workaround for now: workflow-support-plugin/pull/82
  . We
  will release it only as an experimental release for Java11-only
  - To deploy the patch, we will create a temporary update center for
  Java 11 experimental releases (INFRA-1870
  ). The approach is
  confirmed with the Jenkins infrastructure team members
  - Users of standard and experimental Jenkins update centers will not
  see the experimental release, because it will be filtered out there.
  JEP-211 will document the process
  -
*Blocker 2. Docker packaging - OK *
  - Jenkins master and 3 agent packages now offer the "jdk11" tags as
  well as versioned releases (e.g. "2.154-jdk11"). Thanks to
Baptiste, Carlos
  and Olivier for that!
  - There is an open action item for the BlueOcean packaging, but we
  ship experimental versions in
  https://hub.docker.com/r/jenkins/jenkins-experimental/ based on this
  repo
  
.
  It is enough for the preview availability announcement
  -
*Blocker 3. Testing and test automation - OK *
  - Jenkins Core CI flow includes testing with JDK 11 for almost 1
  month (link
  

  )
  - Jenkins Acceptance Test Harness now runs for both Java 8 and Java
  11, thanks to Lucie, Oliver and Ramon for this effort. There is no major
  regressions discovered (link
  )
  - Jenkins Plugin POMs have been updated to support building plugins
  with OpenJDK11. Plugin POM 3.29 is recommended
  - Jenkins Pipeline Library was updated to support testing with Java
  11 in buildPlugin() and other steps (example
  )
  - Plugin Compatibility Tester now supports Java 11 in both CLI and
  Docker modes, we are executing tests against the recommended plugins. So
  far so good
  - There was a LOT of exploratory testing performed, starting Java 10
  and 11-ea testing in June 2017. We confirmed that all major functionality
  works correctly on both Linux and Windows. In particular, plugins like
  Pipeline, JobDSL, JCasC were tested. Maven Integration plugin also works
  well with Java 

Re: Alternative directory implementation of ArtifactManager?

[Staffan Forsell]

Well for us such retention policys does not apply and the time to keep 
artifacts is better handled though jenkins since it created them, than by 
other time based policies. We typically keep a number of artifacts per job 
while some builds are kept forever, typically release builds for 
traceability.
Well now I got most of it working but I discovered in my unit tests that 
deleting the job does not remove the artifacts, but removing the build does.
It seems that removing the job only recursively removed the job directory, 
see hudson.model.Job#delete.
To me this seems like a bug, it makes it harder to clean clean artifacts 
for a custom ArtifactsManager.
I managed to get around it using ItemListener.onDelete() to call 
run.deleteArtifacts() but I kind of think that this should be jenkins own 
responsibility while deleting a job.
Should I file an issue or do you have an other opinion?

On Tuesday, 4 December 2018 16:37:26 UTC+1, Jesse Glick wrote:
>
> On Tue, Dec 4, 2018 at 3:48 AM Staffan Forsell  > wrote: 
> > How are moves and renames handled? E.g. if a admin moves a job to a 
> folder? How does the ArtifactManager handle this? 
>
> For `StandardArtifactManager`, that would be implicit in the job 
> directory itself moving. For others, including `artifact-manager-s3`, 
> this is not handled automatically. `JCloudsArtifactManager.key` could 
> perhaps be made non-`transient` to track the originally stored 
> location, or there could be an `ItemListener.onLocationChanged` to 
> physically relocate the blob(s), or the `unique-id` plugin could be 
> relied on for another key which persists across moves. For now we 
> decided to keep things simple and transparent—there is a predictable 
> blob location based on what you see in Jenkins—and just punt on the 
> use case of historical builds preceding a move/rename. 
>
> (On a related note, by default `artifact-manager-s3` declines to 
> remove artifacts after build deletion in Jenkins, on the grounds that 
> AWS retention policies and Glacier migration are likely better, and we 
> want the Jenkins master to require minimal IAM permissions: a 
> compromised master should not be able to destroy or alter cloud data.) 
>

-- 
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/c4e02423-e915-44b2-a5bc-0f2280b3764b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Discussion: Community Onboarding/Outreach and Advocacy SIGs

[Liam Newman]

"... related.  I'd rather keep them together even with the scope being a 
bit broad."  
(don't know what happened there. CTRL-X misfire.)

On Wednesday, December 5, 2018 at 10:55:41 AM UTC-8, Liam Newman wrote:
>
> Oleg, 
> I understand your point that Outreach and Advocacy feel like separate 
> areas, but they are closely related.  However, I'd together even with the 
> scope being a bit broad.  
>
> I think that everyone in an Advocacy SIG would need to also be part of an 
> Outreach SIG - IMO a core aspect of advocacy for Jenkins is outreach.  To 
> some extent, I think calling the SIG "Advocacy and Outreach" is almost 
> redundant - except that, for the sake of new user outreach it is important 
> to specify "Outreach" in the name of the SIG. :) 
>
> Reversing that, people that are interested in working on Outreach and new 
> user experience will generally need to be involved in discussions around 
> Advocacy. We have sub-channels (and SIGs) for some outreach projects 
> already. 
>
> Does anyone else have strong feeling either way? 
>
> As a separate question: Who are potential owners of the SIG(s)?
>
> Some candidates:
>
>- Oleg Nenashev
>- Tracy Miranda 
>- Liam Newman
>- (your name here - any voluteers?)
>
>
> Thanks,
> Liam N. 
>
> On Monday, December 3, 2018 at 11:03:16 PM UTC-8, Oleg Nenashev wrote:
>>
>> My preference for structure would be as 1 SIG (called Outreach or 
>>> Outreach & Advocacy) which is an umbrella for initiatives like GSoC, 
>>> Outreachy, Hacktoberfest. 
>>>
>>
>> I definitely agree with such scope if it is an "Outreach" SIG.
>> But I do not see a lot of "Advocacy" in this scope TBH (Wikipedia 
>> ).
>>
>>1. We do not manage social media
>>2. We do not work with Jenkins Ambassadors
>>3. This SIG does not coordinate JAMs, JOMs and other similar events
>>4. ... // whatever other stuff from the first message (scope is 
>>definitely bloated there)
>>
>> Please correct me if I am wrong.
>>
>> Liam, your proposal was to actually have an Advocacy SIG IIRC. If we go 
>> forward with the Outreach SIG, we still might create an Advocacy SIG. How 
>> do you see it?
>>
>> Best regards,
>> Oleg
>>  
>> On Tuesday, December 4, 2018 at 1:19:39 AM UTC+1, Liam Newman wrote:
>>>
>>> I'm also plus +1, Tracy.
>>>
>>> I'm a little concerned about over-broad scope.  But was can always 
>>> adjust it as we go along. 
>>>
>>>
>>> On Monday, December 3, 2018 at 8:49:35 AM UTC-8, R Tyler Croy wrote:

 (replies inline) 

 On Mon, 03 Dec 2018, Tracy Miranda wrote: 

 > This sounds great. 
 > 
 > My preference for structure would be as 1 SIG (called Outreach or 
 Outreach 
 > & Advocacy) which is an umbrella for initiatives like GSoC, 
 Outreachy, 
 > Hacktoberfest. 
 > 
 > GSoC, Outreachy should maintain their own channels i.e. gitter, etc 
 so 
 > those who want to just focus on those can do so. But then at the SIG 
 level 
 > we cover more topics (as listed in the email) share best practices 
 and 
 > foster wider collaboration across initiatives for those who would 
 like to 
 > do so. 


 This sounds good to me Tracy, +1 


 -- 
 GitHub:  https://github.com/rtyler 

 GPG Key ID: 0F2298A980EE31ACCA0A7825E5C92681BEF6CEA2 

>>>

-- 
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/6f927b51-ec35-423c-abda-21e7976b0d41%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Discussion: Community Onboarding/Outreach and Advocacy SIGs

[Liam Newman]

Oleg, 
I understand your point that Outreach and Advocacy feel like separate 
areas, but they are closely related.  However, I'd together even with the 
scope being a bit broad.  

I think that everyone in an Advocacy SIG would need to also be part of an 
Outreach SIG - IMO a core aspect of advocacy for Jenkins is outreach.  To 
some extent, I think calling the SIG "Advocacy and Outreach" is almost 
redundant - except that, for the sake of new user outreach it is important 
to specify "Outreach" in the name of the SIG. :) 

Reversing that, people that are interested in working on Outreach and new 
user experience will generally need to be involved in discussions around 
Advocacy. We have sub-channels (and SIGs) for some outreach projects 
already. 

Does anyone else have strong feeling either way? 

As a separate question: Who are potential owners of the SIG(s)?

Some candidates:

   - Oleg Nenashev
   - Tracy Miranda 
   - Liam Newman
   - (your name here - any voluteers?)
   
   
Thanks,
Liam N. 

On Monday, December 3, 2018 at 11:03:16 PM UTC-8, Oleg Nenashev wrote:
>
> My preference for structure would be as 1 SIG (called Outreach or Outreach 
>> & Advocacy) which is an umbrella for initiatives like GSoC, Outreachy, 
>> Hacktoberfest. 
>>
>
> I definitely agree with such scope if it is an "Outreach" SIG.
> But I do not see a lot of "Advocacy" in this scope TBH (Wikipedia 
> ).
>
>1. We do not manage social media
>2. We do not work with Jenkins Ambassadors
>3. This SIG does not coordinate JAMs, JOMs and other similar events
>4. ... // whatever other stuff from the first message (scope is 
>definitely bloated there)
>
> Please correct me if I am wrong.
>
> Liam, your proposal was to actually have an Advocacy SIG IIRC. If we go 
> forward with the Outreach SIG, we still might create an Advocacy SIG. How 
> do you see it?
>
> Best regards,
> Oleg
>  
> On Tuesday, December 4, 2018 at 1:19:39 AM UTC+1, Liam Newman wrote:
>>
>> I'm also plus +1, Tracy.
>>
>> I'm a little concerned about over-broad scope.  But was can always adjust 
>> it as we go along. 
>>
>>
>> On Monday, December 3, 2018 at 8:49:35 AM UTC-8, R Tyler Croy wrote:
>>>
>>> (replies inline) 
>>>
>>> On Mon, 03 Dec 2018, Tracy Miranda wrote: 
>>>
>>> > This sounds great. 
>>> > 
>>> > My preference for structure would be as 1 SIG (called Outreach or 
>>> Outreach 
>>> > & Advocacy) which is an umbrella for initiatives like GSoC, Outreachy, 
>>> > Hacktoberfest. 
>>> > 
>>> > GSoC, Outreachy should maintain their own channels i.e. gitter, etc so 
>>> > those who want to just focus on those can do so. But then at the SIG 
>>> level 
>>> > we cover more topics (as listed in the email) share best practices and 
>>> > foster wider collaboration across initiatives for those who would like 
>>> to 
>>> > do so. 
>>>
>>>
>>> This sounds good to me Tracy, +1 
>>>
>>>
>>> -- 
>>> GitHub:  https://github.com/rtyler 
>>>
>>> GPG Key ID: 0F2298A980EE31ACCA0A7825E5C92681BEF6CEA2 
>>>
>>

-- 
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/02b0a0fc-224c-46da-b137-ddbea3738e5c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Trademark sublicense request: CloudBees Jenkins X Support

[James Nord]

I see no reason why we should treat "Jenkins X" with different rules from 
"Jenkins", and as such given this follows the trend of usage already 
approved here is my +1


On Tuesday, November 27, 2018 at 3:10:56 PM UTC, Tracy Miranda wrote:
>
> Hi all,
>
> On behalf of CloudBees, I’d like to request the permission to use the 
> following name that uses ‘Jenkins’ in it:
>
>- CloudBees Jenkins X Support
>
> This will be a name of a support offering (not a product) for Jenkins X 
> support from CloudBees. 
> This is inclusive of all the services components provided: s support 
> personnel, knowledgebase, CSM interaction, docs, etc.  
>
> The aim has been to keep this consistent with existing names already 
> approved including previously approved CloudBees Jenkins Support. 
>
> I will add this as an agenda item for Dec 5th project governance meeting 
> to be able to get a decision there. If you have any concerns or objections, 
> please chime in on this thread prior to the meeting, so that we can address 
> them.
>
> Tracy
>

-- 
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/c2a8bf27-6fac-4f7d-a690-e846fcde5e3c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Trademark sublicense request: CloudBees Jenkins X Support

[Parker Ennis]

+1. Will be great for consistency and continuing to improve the 
collaboration with the community to make Jenkins X the best it can be. A 
testament to the bright future ahead.


On Tuesday, November 27, 2018 at 10:10:56 AM UTC-5, Tracy Miranda wrote:
>
> Hi all,
>
> On behalf of CloudBees, I’d like to request the permission to use the 
> following name that uses ‘Jenkins’ in it:
>
>- CloudBees Jenkins X Support
>
> This will be a name of a support offering (not a product) for Jenkins X 
> support from CloudBees. 
> This is inclusive of all the services components provided: s support 
> personnel, knowledgebase, CSM interaction, docs, etc.  
>
> The aim has been to keep this consistent with existing names already 
> approved including previously approved CloudBees Jenkins Support. 
>
> I will add this as an agenda item for Dec 5th project governance meeting 
> to be able to get a decision there. If you have any concerns or objections, 
> please chime in on this thread prior to the meeting, so that we can address 
> them.
>
> Tracy
>

-- 
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/eef1b4fb-5b83-4293-958c-576cecd5e448%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Plugin adoption] Audit Trail Plugin

[Pierre BEITZ]

Hello

I guess the timeout expired :) I'll prepare a PR in the infra repo to
update the permission file.

Thanks

On Thu, Nov 15, 2018 at 9:31 PM Oleg Nenashev 
wrote:

> Hi,
>
> Thanks for the interest!
> Let's wait for the response from Tomasz. Usually we set a 2-week response
> timeout in such cases.
>
> Best regards,
> Oleg
>
> On Wednesday, November 14, 2018 at 10:48:46 PM UTC+1, Pierre BEITZ wrote:
>>
>> Hello,
>>
>> I'd like to be made maintainer of the Audit Trail Plugin
>> . I tried to ping
>> Tomasz the maintainer several time on this PR
>> 
>> without success. Added him to this thread too in case he missed the github
>> notifications.
>>
>> Github handle: PierreBtz
>> Jenkins infrastructure account id: pierrebtz
>>
>> Thanks
>>
> --
> 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/155260b4-38d6-46ef-acf7-e9b26b4a985a%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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAH6Pko%2BiruCnvVDOBs37ocT9yrhfyexwXeR7cF3t3-wPkXj%2BnA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Trademark sublicense request: CloudBees Jenkins X Support

[jrawlings]

+1 from me

On Wednesday, December 5, 2018 at 5:09:55 PM UTC, jstr...@cloudbees.com 
wrote:
>
> +1 from me too
>
> On Tuesday, November 27, 2018 at 3:10:56 PM UTC, Tracy Miranda wrote:
>>
>> Hi all,
>>
>> On behalf of CloudBees, I’d like to request the permission to use the 
>> following name that uses ‘Jenkins’ in it:
>>
>>- CloudBees Jenkins X Support
>>
>> This will be a name of a support offering (not a product) for Jenkins X 
>> support from CloudBees. 
>> This is inclusive of all the services components provided: s support 
>> personnel, knowledgebase, CSM interaction, docs, etc.  
>>
>> The aim has been to keep this consistent with existing names already 
>> approved including previously approved CloudBees Jenkins Support. 
>>
>> I will add this as an agenda item for Dec 5th project governance meeting 
>> to be able to get a decision there. If you have any concerns or objections, 
>> please chime in on this thread prior to the meeting, so that we can address 
>> them.
>>
>> Tracy
>>
>

-- 
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/26de20fd-f7b2-48d4-8dca-ce9c3959566a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Trademark sublicense request: CloudBees Jenkins X Support

[jstrachan]

+1 from me too

On Tuesday, November 27, 2018 at 3:10:56 PM UTC, Tracy Miranda wrote:
>
> Hi all,
>
> On behalf of CloudBees, I’d like to request the permission to use the 
> following name that uses ‘Jenkins’ in it:
>
>- CloudBees Jenkins X Support
>
> This will be a name of a support offering (not a product) for Jenkins X 
> support from CloudBees. 
> This is inclusive of all the services components provided: s support 
> personnel, knowledgebase, CSM interaction, docs, etc.  
>
> The aim has been to keep this consistent with existing names already 
> approved including previously approved CloudBees Jenkins Support. 
>
> I will add this as an agenda item for Dec 5th project governance meeting 
> to be able to get a decision there. If you have any concerns or objections, 
> please chime in on this thread prior to the meeting, so that we can address 
> them.
>
> Tracy
>

-- 
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/7e1815b5-f2ff-41e8-81f7-80adb251106e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Own Cloud Plugin: "ClassNotFoundException: javax.servlet.ServletException" when running job for the first time

[Johannes Schneider]

Hi Jesse,

could you give me a hint how to try it out?
I tried 

mvn hpi:run -Djenkins.version=2.154-rc27545.0e85c9fb206a

which does not work (of course) because I don't have a snapshot repository 
configured. A quick search didn't give me
the the URL for the snapshot repository. Could you help me out?


Am Dienstag, 27. November 2018 16:58:26 UTC+1 schrieb Jesse Glick:
>
> it should deploy an incremental version 
> 2.154-rc27545.0e85c9fb206a which you can use as `jenkins.version` in 
> your POM (or passing via `-D` to `hpi:run`). 
>

-- 
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/e2ac800c-0ae7-4edb-9cfd-423c655ba605%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Trademark sublicense request: CloudBees Jenkins X Support

[Oleg Nenashev]

Since these is already "CloudBees Jenkins Support" has been already 
approved, I see no reason why it cannot be approved from the process 
standpoint.
So +1 from me

On Tuesday, November 27, 2018 at 4:10:56 PM UTC+1, Tracy Miranda wrote:
>
> Hi all,
>
> On behalf of CloudBees, I’d like to request the permission to use the 
> following name that uses ‘Jenkins’ in it:
>
>- CloudBees Jenkins X Support
>
> This will be a name of a support offering (not a product) for Jenkins X 
> support from CloudBees. 
> This is inclusive of all the services components provided: s support 
> personnel, knowledgebase, CSM interaction, docs, etc.  
>
> The aim has been to keep this consistent with existing names already 
> approved including previously approved CloudBees Jenkins Support. 
>
> I will add this as an agenda item for Dec 5th project governance meeting 
> to be able to get a decision there. If you have any concerns or objections, 
> please chime in on this thread prior to the meeting, so that we can address 
> them.
>
> Tracy
>

-- 
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/ec85b2e4-c6d6-4fda-8586-5a03d43cb21f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: GSoC proposal about the Multi-branch for Gitlab

[arch]

Agree with this.

On Tue, Dec 4, 2018 at 8:19 PM Oleg Nenashev  wrote:

> Hi Rick,
>
> Thanks for starting this discussion! I think it is good to be published as
> a draft project idea on jenkins.io.
> I suggest to also bring up this topic in the Pipeline Authoring SIG (e.g.
> just adding it to CC).
>
> Best regards,
> Oleg
>
> On Tuesday, December 4, 2018 at 2:52:54 AM UTC+1, Rick wrote:
>>
>> hi:
>>
>> I made a proposal about the Multi-branch support for Gitlab.
>>
>> Here is the doc link.
>>
>> https://docs.google.com/document/d/1Gqz4LyU5sw6I50OdAVsQSW_WPNDlvXg4Ic9NdcYj4Ts/edit?usp=sharing
>>
>> Any comments are welcome.
>>
>> Thanks,
>> Rick
>>
> --
> 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/d922ea0c-b372-4da2-b85f-7616c8fd6d95%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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAMM7nTEAqPePA29rcwzArnTKH4ndTrJhieNbabhX9yqhk_Sb5Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.