[
https://issues.apache.org/jira/browse/BEAM-4838?focusedWorklogId=126582&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-126582
]
ASF GitHub Bot logged work on BEAM-4838:
----------------------------------------
Author: ASF GitHub Bot
Created on: 24/Jul/18 12:02
Start Date: 24/Jul/18 12:02
Worklog Time Spent: 10m
Work Description: lgajowy commented on issue #5989: [BEAM-4838] Add
dockerfile for standalone Jenkins. Plugins included.
URL: https://github.com/apache/beam/pull/5989#issuecomment-407381205
@Ardagan ok, one last thing that I think is worth clarifying:
I tested this code locally and was able to run jobs from my repo and from
master too. However, I was not able to finish them successfully due to errors
like:
> [EnvInject] - Variables injected successfully.
FATAL: Could not find credentials entry with ID 'beam-coveralls-token'
or when I commented out the "culprit" above i was missing the `gcloud` tool:
> /tmp/jenkins6722263981257365856.sh: 2: /tmp/jenkins6722263981257365856.sh:
gcloud: not found
This is totally understandable, because the dockerized jenkins does not have
gcloud installed nor should have coveralls-token anywhere (unless provided
later). Also, the current setup is enough to test job dsl scripts. Still, since
seeing the success in job might be temptping, do you think it is a good idea to
add an explicit note that some tools (like gcloud) still need to be installed
manually for the jobs to fully work?
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 126582)
Time Spent: 4h 50m (was: 4h 40m)
> Prepare instructions for running Jenkins locally.
> -------------------------------------------------
>
> Key: BEAM-4838
> URL: https://issues.apache.org/jira/browse/BEAM-4838
> Project: Beam
> Issue Type: Improvement
> Components: build-system
> Reporter: Mikhail Gryzykhin
> Assignee: Mikhail Gryzykhin
> Priority: Major
> Time Spent: 4h 50m
> Remaining Estimate: 0h
>
> We need a way to test Jenkins Job DSL scripts without breaking our build
> server. One of the approaches available is to spin up Jenkins on your local
> machine with all plugins available.
> This has already been used by some developers in their workflow.
> We want to share instruction on spinning up local Jenkins with other
> developers.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
