[OpenStack-Infra] Final Thoughts on Internship

[Kien Ha]

Hello,


Today is the final day of my internship and so I have decided to leave my
thoughts of working on Jenkins Job Builder (JJB) and with the community.

When I first started working on JJB, I had very basic programming knowledge
and with limited to none knowledge on Git, GitHub, and Gerrit. My goal for
the internship was to expand my knowledge and gain some work experience in
an open source environment. Over the last 3 months of working on the JJB
project, I have acquired essential skills such as using Git and Gerrit,
ways to problem solve, and improve my programming skills.

I have also gained valuable experience on how the open source community
work together. Because of the nature of having to review patches on Gerrit
before merging any patches into the main branch, I was able to improve and
write better code from reviews given by experts and more experienced
programmers. Their perspectives and thoughts when problems arises were
valuable as more often than not, I would have not thought of or considered.
I like JJB’s documentation since it is often consistent, and concise. This
allows me to rely on the documentation while I am working.The open source
community has been friendly and helpful whenever I needed help. They are
always willing to help wherever they can.

I think however, that patches are slow to be reviewed on. There are many
patches that are weeks old. Few patches are months, and even a year old.

Working on JJB, I have attained more than my goals and expectations as I
have become a core reviewer of JJB. I plan on continuing to contribute
wherever I can after this internship is over.

Thank you JJB team, OpenStack, OpenDayLight, and the rest of the community
for the internship. It has been a great experience.

Attached below is a link to my JJB project proposal document with a
complete table of plugins that I have worked on and weekly work log found
at the bottom of the document [1].

[1]
https://docs.google.com/document/d/17AHluxqiBFcsTCkpyekDOFSTahX50pXFmQgjlK-PoEQ/edit
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

[OpenStack-Infra] Jenkins Job Builder status report

[Kien Ha]

Hello,

I had the opportunity to attend Linux Con for educational purposes and I
learned a lot during my time there. And so most of my time was dedicated to
the learning opportunity that was given to me.

This week, I have:
- Switch to import module instead of function in properties
- Update TestNG to use valid_dict property of convert xml

Attached below is a link to my JJB project proposal document with a
complete table of plugins that I have worked on and weekly work log found
at the bottom of the document [1].

[1]
https://docs.google.com/document/d/17AHluxqiBFcsTCkpyekDOFSTahX50pXFmQgjlK-PoEQ/edit
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

[OpenStack-Infra] Jenkins Job Builder status report

[Kien Ha]

Hi,

This week, I have:
- Update docker build publish to use convert xml
- Update runscope plugin to use convert xml
- Update maven-builder to use convert xml
- Update cfp builder to use convert xml
- Update findbugs_settings to use convert xml
- Update helpers.artifactory
- Fix issue that cause JCloud instance to be set
- Update jdepend to use convert xml
- Update Summary Display plugin to use convert xml
- Update disable-failed-job to use convert xml
- Update hipchat plugin to use convert xml
- Add missing docs for maven-targets
- Fix typo for reporters doc

Next week I have an exam on Friday, August 19, and so I'll be busy for most
of my days. I will be available as often as I can if anything is needed.

Attached below is a link to my JJB project proposal document with a
complete table of plugins that I have worked on and weekly work log found
at the bottom of the document [1].

[1] https://docs.google.com/document/d/17AHluxqiBFcsTCkpyekDOFSTahX50
pXFmQgjlK-PoEQ/edit
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

[OpenStack-Infra] Jenkins Job Builder status report

[Kien Ha]

Hi,

This week, I have:
- Add support for Growl plugin
- Add support for Cloud Foundry plugin
- Add support for Keivox KMAP plugin
- Update properties.slack to use convert xml
- Update cobertura to use convert xml
- Update Build Name Setter plugin to use convert xml

Next week:
- Update Docker Build Publish plugin
- Update runscope plugin
- Add support for klocwork plugin

Attached below is a link to my JJB project proposal document with a
complete table of plugins that I have worked on and weekly work log found
at the bottom of the document [1].

[1]
https://docs.google.com/document/d/17AHluxqiBFcsTCkpyekDOFSTahX50pXFmQgjlK-PoEQ/edit
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

[OpenStack-Infra] Jenkins Job Builder status report

[Kien Ha]

Hello,

This week, I have:
- Add support for Fingerprint plugin
- Add support for CodeCover plugin
- Update Delivery Pipeline plugin to use convert xml
- Update rebuild plugin to use convert xml
- Add support for FTP-Publisher plugin
- Fix link to findbugs minimal example
- Update HTML Publisher plugin to use convert xml
- Update EnvInject plugin
- Update LogStash plugin to use convert xml
- Add GitBucket plugin support
- Add display-name option to github plugin
- Update Cobertura docs to be 4 space indent syntax
- Update FindBugs docs to 4 space indent syntax
- Remove handle_entity_children for convert xml

Next week:
- Add Cloud Foundry plugin support
- Add Growl plugin support
- Add Keivox KMAP plugin support

Attached below is a link to my JJB project proposal document with a
complete table of plugins that I have worked on and weekly work log found
at the bottom of the document [1].

[1]
https://docs.google.com/document/d/17AHluxqiBFcsTCkpyekDOFSTahX50pXFmQgjlK-PoEQ/edit
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] Jenkins job builder status report

[Kien Ha]

Hey Antoine,

Thanks for the feedback and noticing!

Sincerely,
Kien Ha

On Sat, Jul 16, 2016 at 2:43 AM, Antoine Musso <has...@free.fr> wrote:

> On 16/07/16 05:46, Kien Ha wrote:
>
>> Hello,
>>
>> This week, I have:
>> - Update TestFairy plugin
>> - Update clang scan build
>> - Update check for valid attributes for SonaType CLM
>> - Update RunDeck plugin to use convert xml
>> - Update scoverage plugin to use convert xml
>> - Update DRY plugin to use convert xml function
>> - Update clamav plugin to use convert xml
>> - Update WhiteSource plugin
>> - Update Repo plugin to use convert_mapping_to_xml
>> - Update live-screenshot plugin to use convert xml
>> - Update Logfilesizechecker to use convert xml
>> - Update MongoDB plugin
>>
>> Next week, I plan on:
>> - updating gitlab trigger to support "trigger-open-merge-request-push"
>> options
>> - removing fail_required parameter from convert_mapping_to_xml function
>> after a few plugins that uses this function reviewed and merged.
>>
>> Linked below is my JJB project proposal document with a complete table
>> of plugins that I have worked on and weekly work log found at the bottom
>> of the document [1].
>>
>> Regards,
>> Kien Ha
>>
>> [1]
>> https://docs.google.com/document/d/17AHluxqiBFcsTCkpyekDOFSTahX50pXFmQgjlK-PoEQ/edit
>>
>
> Hello Kien,
>
> I find that document and the weekly report to be totally awesome!  Thank
> you for taking care of updating so many JJB plugins support!
>
> --
> Antoine "hashar" Musso
>
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

[OpenStack-Infra] Jenkins job builder status report

[Kien Ha]

Hello,

This week, I have:
- Update TestFairy plugin
- Update clang scan build
- Update check for valid attributes for SonaType CLM
- Update RunDeck plugin to use convert xml
- Update scoverage plugin to use convert xml
- Update DRY plugin to use convert xml function
- Update clamav plugin to use convert xml
- Update WhiteSource plugin
- Update Repo plugin to use convert_mapping_to_xml
- Update live-screenshot plugin to use convert xml
- Update Logfilesizechecker to use convert xml
- Update MongoDB plugin

Next week, I plan on:
- updating gitlab trigger to support "trigger-open-merge-request-push"
options
- removing fail_required parameter from convert_mapping_to_xml function
after a few plugins that uses this function reviewed and merged.

Linked below is my JJB project proposal document with a complete table of
plugins that I have worked on and weekly work log found at the bottom of
the document [1].

Regards,
Kien Ha

[1]
https://docs.google.com/document/d/17AHluxqiBFcsTCkpyekDOFSTahX50pXFmQgjlK-PoEQ/edit
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

[OpenStack-Infra] Jenkins job builder status report

[Kien Ha]

Hi,

This week, I have:
- Add valid set of options parameter to convert xml
- Update TestFairy plugin
- Update support for BuildResultTrigger plugin
- Update FSTrigger plugin
- Update JaCoCo plugin
- Clean up import helpers in publishers
- Update grails plugin
- Update sbt plugin to use convert_mapping_to_xml
- Update build-discarder to use convert xml
- Update TAP plugin
- Update TestNG plugin

Next week:
- continue to work and add "valid set of options parameter" to convert xml
- update Clang Scan-build plugin
- update RunDeck plugin
- update scoverage plugin

Attached below is a link to my JJB project proposal document with a
complete table of plugins that I have worked on and weekly work log found
at the bottom of the document [1].

Regards,
Kien Ha

[1]
https://docs.google.com/document/d/17AHluxqiBFcsTCkpyekDOFSTahX50pXFmQgjlK-PoEQ/edit
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] JJB V2.0 planning

[Kien Ha]

I am fine with starting this Friday. I am also okay with starting any time
afterwards too.

On Wed, Jul 6, 2016 at 3:14 PM, Darragh Bailey 
wrote:

>
> Sounds like Friday is the clear winner. Do we want to stay this Friday? Or
> would everyone prefer a bit more notice to plan things with their other
> work?
>
> I'm not around Friday 15th, but it could start then anyway if others are
> happy (might need one more core to help land stuff that day)? Otherwise
> could wait until the 22nd, naturally can still do normal reviews in the
> mean time.
>
> --
> Darragh Bailey
> "Nothing is foolproof to a sufficiently talented fool" - unknown
> On 6 Jul 2016 08:31, "Dong Ma"  wrote:
>
>> Hey Darragh,
>>
>> For Mon/Fri, the current time slots both works for me.
>>
>> Thanks,
>> Dong
>>
>>
>>
 On Mon, Jul 4, 2016 at 8:47 PM, Dong Ma 
 wrote:

> Hey Darragh,
>
>
>
> I agree with your thought and would like to participate to the
> reviews, although the time slots is a little late for me but it works.
>
>
>

>>> Would moving the time slot an hour earlier on either Mon/Fri suit you
>>> better?
>>>
>>> --
>>> Darragh Bailey
>>> "Nothing is foolproof to a sufficiently talented fool"
>>>
>>
>>
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] Jenkins job builder status report

[Kien Ha]

Hi Dong,

Looks like I misinterpreted what you mean the first time around, sorry
about that. To clarify, did you mean to keep track of changes made to
convert to xml function or to keep track of the plugins that have been
updated to use the function? If it is wanted, I can go ahead and start
adding it to the commit messages.

Thanks,
Kien

On Sun, Jul 3, 2016 at 5:13 AM, Dong Ma <winterma.d...@gmail.com> wrote:

> Hey Darragh and Kien,
>
> What I proposed is to create a etherpad/spec/blueprint to cover these
> changes of using the convert to xml function in JJB, and include it in the
> commit message as reference to keep tracking the process, so if someone
> else would like to contribute, it will be easy to find it.
>
> Yes, include the document link into the commit message is not a good
> commit message, I agree to keep the commits describing the functional
> reason.
>
> Thanks,
> Vincent
>
> 2016-07-01 22:25 GMT+08:00 Darragh Bailey <daragh.bai...@gmail.com>:
>
>> Hi Kien,
>>
>>
>> I missed this email, but spotted this appearing in recent commits.
>>
>>
>> On 13 June 2016 at 03:28, Kien Ha <kienha9...@gmail.com> wrote:
>>
>>>
>>> On Sat, Jun 11, 2016 at 11:12 PM, Dong Ma <winterma.d...@gmail.com>
>>> wrote:
>>>
>>>> Hello Kien Ha,
>>>>
>>>> Thanks for the contribution to the Jenkins job builder projects, have
>>>> one comment here, how about add your proposal document link or create a new
>>>> etherpad into the commit message of each patches as reference to keep
>>>> tracking the process.
>>>>
>>>> Vincent
>>>>
>>>
>> This kind goes outside of what is generally described as
>> https://wiki.openstack.org/wiki/GitCommitMessages#Information_in_commit_messages
>>
>>
>> The update to the mailing list is more than enough, let's keep the
>> commits describing the functional reason for the change, or if there is a
>> separate proposal spec/blueprint that covers changing to use the convert to
>> xml function in JJB, changes relevant can include a reference, otherwise
>> lets keep the commit messages focused on the change itself.
>>
>>
>> --
>> Darragh Bailey
>> "Nothing is foolproof to a sufficiently talented fool"
>>
>
>
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] JJB V2.0 planning

[Kien Ha]

HI Darragh,

I would like to help where I can in the reviews, but Tuesdays and Thursdays
are my busiest days. I can only guarantee that I am free after 19:00 UTC on
Tuesdays and Thursdays. Monday and Fridays are days where I am free from
summer class obligations but I am not too sure if that will work with
everyone else.

Regards,
Kien Ha

On Mon, Jul 4, 2016 at 8:47 PM, Dong Ma <winterma.d...@gmail.com> wrote:

> Hey Darragh,
>
>
>
> I agree with your thought and would like to participate to the reviews,
> although the time slots is a little late for me but it works.
>
>
>
> Thanks,
>
> Dong Ma (Vincent)
>
>
>
> Email: winterma.d...@gmail.com
>
> IRC: larainema
>
> Telephone: +86 18610023880
>
>
>
>
> 2016-07-05 0:43 GMT+08:00 Darragh Bailey <daragh.bai...@gmail.com>:
>
>> Hi,
>>
>>
>> To try and minimise trashing of both core reviews and V2.0 patch
>> author(s), I'd like to propose that we pick a time/day every second week
>> for 3-4 iterations where those interested set aside a set block of time to
>> collaborate in getting the main rework patches landed. Consider it a set of
>> mini bug days focused on JJB 2.0 API changes.
>>
>> To get the ball rolling, I'm going to suggest one of the following 2
>> timezones (obviously these suit me best, but I'm available the other days
>> as well):
>> 14:00-1800 UTC Thurs (Staring 7th July - not available the 14th hence
>> suggesting this Thurs)
>> 14:00-1800 UTC Tues (Staring 12th July)
>>
>> I'm assuming that later in the day for me aligns better with others, but
>> I could be very wrong.
>>
>> Also thinking that spinning up a temporary public dedicated IRC chat room
>> would be helpful here, probably look to avoid using one of the existing
>> meeting rooms because I'm assuming that would conflict with other teams,
>> unless someone tells me there is a simple solution to this. Only negative I
>> can see is that the chats wouldn't be logged.
>>
>>
>>
>> More info below on why suggest this:
>>
>>
>> Having gone through a few cycles where patches get reviewed, reworked and
>> then broken by other changes landing, reworked again, reviewed and broken
>> again, it can be quite onerous on both author and reviewer getting a change
>> that touches a number of places to land as the risk of another patch
>> landing causing a merge failure increases dramatically the more places the
>> patch touches.
>>
>> The set of V2 patches has to bring the existing code through some amount
>> of interim steps to make it easy to review, unfortunately given the amount
>> of rework to do, the odds of anything else triggering a conflict is pretty
>> high and basically faced with the following choices:
>>
>>- Take a long time complete the cycle of rework -> review -> rework
>>-> break -> rework ->. ...
>>- Block landing any changes that touch any of the code impacted by V2
>>work until most V2 patches are landed.
>>
>>
>>
>> However we can get enough cores on around the same time and try for some
>> synchronized collaboration, I think it's probably far easier to land a
>> series of patches over a few meetings and get everything far enough along
>> with much less workload placed on everyone involved that we can then revert
>> back to the more async approach without the same issues around the
>> remaining changes.
>>
>> Expect that this would only take 3-4 of these to get the major part of
>> the rewrite in place.
>>
>> Thoughts? Does this work for enough other JJB reviewers?
>>
>>
>> --
>> Darragh Bailey
>> "Nothing is foolproof to a sufficiently talented fool"
>>
>> ___
>> OpenStack-Infra mailing list
>> OpenStack-Infra@lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
>>
>>
>
> ___
> OpenStack-Infra mailing list
> OpenStack-Infra@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
>
>
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

[OpenStack-Infra] Jenkins job builder status report

[Kien Ha]

Hello,

This week, I have:
- Update Copy Artifact plugin to use convert xml
- Update doxygen plugin to use convert xml
- Update OpenShift Pipeline plugin
- Update GitHub pull request builder plugin
- Update bazaar plugin

I am working towards having all plugins that use convert_mapping_to_xml use
fail_required=True argument. I also want to look into improving
convert_mapping_to_xml by having it manage options where the value must be
one from a list as was suggested [1] .

Attach below is a link to my Jenkins job builder project proposal document
with a complete table of plugins that I have worked on found at the top of
the document [2]. The weekly work log is found at the bottom of the
document.

Regards,
Kien Ha

[1] https://review.openstack.org/#/c/261587/
[2]
https://docs.google.com/document/d/17AHluxqiBFcsTCkpyekDOFSTahX50pXFmQgjlK-PoEQ/edit
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] Jenkins job builder status report

[Kien Ha]

Hey Darragh,

No problem at all. Thanks for the feedback. I'll slowly start removing them
from my commits and for future patches.

Thanks,
Kien Ha

On Fri, Jul 1, 2016 at 10:25 AM, Darragh Bailey <daragh.bai...@gmail.com>
wrote:

> Hi Kien,
>
>
> I missed this email, but spotted this appearing in recent commits.
>
>
> On 13 June 2016 at 03:28, Kien Ha <kienha9...@gmail.com> wrote:
>
>>
>> On Sat, Jun 11, 2016 at 11:12 PM, Dong Ma <winterma.d...@gmail.com>
>> wrote:
>>
>>> Hello Kien Ha,
>>>
>>> Thanks for the contribution to the Jenkins job builder projects, have
>>> one comment here, how about add your proposal document link or create a new
>>> etherpad into the commit message of each patches as reference to keep
>>> tracking the process.
>>>
>>> Vincent
>>>
>>
> This kind goes outside of what is generally described as
> https://wiki.openstack.org/wiki/GitCommitMessages#Information_in_commit_messages
>
>
> The update to the mailing list is more than enough, let's keep the commits
> describing the functional reason for the change, or if there is a separate
> proposal spec/blueprint that covers changing to use the convert to xml
> function in JJB, changes relevant can include a reference, otherwise lets
> keep the commit messages focused on the change itself.
>
>
> --
> Darragh Bailey
> "Nothing is foolproof to a sufficiently talented fool"
>
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] Jenkins job builder status report

[Kien Ha]

Hey Vincent,

I'll do just that in my future patches.

Thanks,
Kien Ha

On Sat, Jun 11, 2016 at 11:12 PM, Dong Ma <winterma.d...@gmail.com> wrote:

> Hello Kien Ha,
>
> Thanks for the contribution to the Jenkins job builder projects, have one
> comment here, how about add your proposal document link or create a new
> etherpad into the commit message of each patches as reference to keep
> tracking the process.
>
> Vincent
>
> 2016-06-11 4:05 GMT+08:00 Kien Ha <kienha9...@gmail.com>:
>
>> Hello,
>>
>> My name is Kien Ha and I am being mentored by Thanh Ha. I mainly work on
>> the Jenkins Job Builder Project. I was asked to give my status report to
>> the OpenStack.
>>
>> This week I have:
>> - Update Cucumber Reports plugin
>> - Update EnvInject plugin
>> - Update FSTrigger plugin
>> - Update JaCoCo plugin
>> - Update support for BuildResultTrigger plugin
>> - Update Sonatype CLM for CI plugin
>> - External Monitor Job Type is up-to-date
>> - Investigate HTTP Request
>>
>> I was asked to investigate HTTP Request and I found out that it does not
>> have a way to put files onto nexus. It can however delete files on nexus if
>> they are there.
>>
>> Next week I plan on working on:
>> - FindBugs Plugin
>> - Gearman Plugin
>> - IvyTrigger Plugin
>>
>> I have a final exam next week so I will be more focused on my studies.
>>
>> Attach below is a link to my Jenkins job builder project proposal
>> document with a complete table of plugins that I have worked on found at
>> the top of the document [0]. The weekly work log is found at the bottom of
>> the document.
>>
>> Regards,
>> Kien Ha
>>
>> [0]
>> https://docs.google.com/document/d/17AHluxqiBFcsTCkpyekDOFSTahX50pXFmQgjlK-PoEQ/edit
>>
>> ___
>> OpenStack-Infra mailing list
>> OpenStack-Infra@lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
>>
>>
>
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

[OpenStack-Infra] Jenkins job builder status report

[Kien Ha]

Hello,

My name is Kien Ha and I am being mentored by Thanh Ha. I mainly work on
the Jenkins Job Builder Project. I was asked to give my status report to
the OpenStack.

This week I have:
- Update Cucumber Reports plugin
- Update EnvInject plugin
- Update FSTrigger plugin
- Update JaCoCo plugin
- Update support for BuildResultTrigger plugin
- Update Sonatype CLM for CI plugin
- External Monitor Job Type is up-to-date
- Investigate HTTP Request

I was asked to investigate HTTP Request and I found out that it does not
have a way to put files onto nexus. It can however delete files on nexus if
they are there.

Next week I plan on working on:
- FindBugs Plugin
- Gearman Plugin
- IvyTrigger Plugin

I have a final exam next week so I will be more focused on my studies.

Attach below is a link to my Jenkins job builder project proposal document
with a complete table of plugins that I have worked on found at the top of
the document [0]. The weekly work log is found at the bottom of the
document.

Regards,
Kien Ha

[0]
https://docs.google.com/document/d/17AHluxqiBFcsTCkpyekDOFSTahX50pXFmQgjlK-PoEQ/edit
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra