The project that sounds interesting to me is Simple Pull-Request Job Plugin.
I do not have many ideas about how to start, and I hope we can discuss some
starting points and get some advice.
What will this plugin do? Is it something like this
https://plugins.jenkins.io/ghprb ?
--
Michal
As greed on Governance meeting, the next LTS line will be based on
latest weekly release. That means, there are no backports to be added
for .1 provided we do not discover something urgent that would cause us
to expedite some or reconsider our choice of baseline - which we do not
anticipate.
Nice! good luck Eric, and if you need some clarification I can try to
explain via mail or short online meeting
When is the meetup?
On Wednesday, February 14, 2018 at 9:54:04 PM UTC+1, Eric Smalling wrote:
>
> Sounds like I may need to be the first to try then! :)
>
> On Wed, Feb 14, 2018 at
Hi Andrei
A good place to start is by reading the plugin
tutorial https://wiki.jenkins.io/display/JENKINS/Plugin+tutorial
Or by looking at Jenkins org at Github, here is a simple search for "job"
https://github.com/search?q=org%3Ajenkinsci+language%3Ajava+job
To see similar job plugins
https://jenkins.io/projects/gsoc/gsoc2018-project-ideas/#simple-pull-request-job-plugin
The idea is to create a YAML file similar to Travis' YAML file but it could
properly be extending that plugin since the infrastructure for being a
Github bot is already there :)
Den torsdag den 15. februar
Created https://issues.jenkins-ci.org/browse/INFRA-1501 to follow
On Thursday, January 4, 2018 at 6:51:18 PM UTC+1, Jordi Miguel wrote:
>
> Hi all,
>
> It's been more than one month since last message on this thread and we
> still don't see any progress to unblock development. I'm sure Jan made
On 02/15/2018 10:33 AM, Joseph P wrote:
https://jenkins.io/projects/gsoc/gsoc2018-project-ideas/#simple-pull-request-job-plugin
The idea is to create a YAML file similar to Travis' YAML file but it could
properly be extending that plugin since the infrastructure for being a
Github bot is
Hi
I am Abhishek , currently i am working in SAP labs as a software
developer intern and for development we use jenkins, gerrit etc. I am very
familiar with the jenkins and also experienced unit testing using Junit .
While working I also thought about merging the result of cobertura
Hello Andrei and al,
The simple pull-request plugin is described in more details in the link
kindly posted by Joseph P (thank you Joseph). I have added some ideas to
the detailed proposal
Hey I worked on something similar ( actually exactly the same thing looks
like)
https://github.com/groupon/DotCi
I would like if to help you if you need anything with your project
On Wednesday, February 14, 2018 at 6:43:04 PM UTC-6, Andrei Vînătoru wrote:
>
> Hello Everyone,
>
> My name is
Posting here was correct. I was just adding a parenthetical comment
about extending a bug fix I had developed to work with this plugin as
well; you can disregard my message.
--
You received this message because you are subscribed to the Google Groups
"Jenkins Developers" group.
To unsubscribe
I posted a comment to the doc. The proposal suggests something far
more complex (and ultimately limited) than what you can already do
very easily with a minor extension to Pipeline.
--
You received this message because you are subscribed to the Google Groups
"Jenkins Developers" group.
To
Ah, I just saw Jesse's comment in the proposal doc. I need to do more
research on multi-branch and organization folders. Last time I tried was
already a few years ago.
On Thursday, February 15, 2018 at 9:55:57 AM UTC-5, Jesse Glick wrote:
>>
>> I posted a comment to the doc. The proposal
The next meetup is a week from today, not sure I can pull of researching enough
on this to present on it that fast though. Next month is already booked with
A.Bayer coming in town so the next opportunity would be some time in mid-late
April.
> On Feb 14, 2018, at 2:44 PM, nicolas de loof
yay! +1
I agree with previous comments that it is not ideal to run multiple
processes and that in a kubernetes world this would possibly be a Pod with
two containers, but I think it's important to get something out and
iteratively improve.
A decent user experience today means just one container
+1, very exciting to make Jenkins operatable by newcomers in a matter of
minutes. Having had very recently to drive a newbie to use Jenkins, even if
he was very motivated, I think this is a great initiative. The flexibility
of Jenkins is a great strength for advanced users, but a real difficulty
+1 obviously. Thanks Alex!
2018-02-14 9:41 GMT+01:00 Oleg Nenashev :
> +1 from me.
> Let me know if you need any help with reviews.
>
> вторник, 13 февраля 2018 г., 22:12:06 UTC+1 пользователь slide написал:
>>
>> Hello,
>>
>> I would like to take over maintaining the
Le 15 févr. 2018 21:29, "Baptiste Mathus" a écrit :
+1, very exciting to make Jenkins operatable by newcomers in a matter of
minutes. Having had very recently to drive a newbie to use Jenkins, even if
he was very motivated, I think this is a great initiative. The flexibility
of
On Thu, Feb 15, 2018 at 10:19 AM, martinda wrote:
> My users will never write a Jenkinsfile, ever. But I
> was able to get them to specify a (very) small YAML file.
>
> Maybe you are suggesting that this should be implemented as an open-source
> Pipeline library and
(replies inline)
On Thu, 15 Feb 2018, Carlos Sanchez wrote:
> yay! +1
>
> I agree with previous comments that it is not ideal to run multiple
> processes and that in a kubernetes world this would possibly be a Pod with
> two containers, but I think it's important to get something out and
>
20 matches
Mail list logo