Hello from the Beam project,
We have a Jenkins build that pushes a snapshot jar every 24 hours (if tests
pass) and we would like to have the same for docker images that form a core
part of the Beam project.
Can you advise on the best way to go about this?
I am aware of the use of bintray for Doc
master builds,
> I guess, but the demand hasn't been there.
>
> Now that the scary warning is over ;) bintray's API docs are pretty
> clear, and it shouldn't be too hard to auto-push to it if you need to.
>
> -Joan
>
> - Original Message -
> F
allowed to push to Nexus, but I
assume it should be roughly analogous so the security scenario is no worse.
Context is https://issues.apache.org/jira/browse/INFRA-15382 which is
moving right along.
Kenn
On Fri, Oct 20, 2017 at 2:22 PM, Kenneth Knowles wrote:
> Thanks for the heads up!
>
&g
On the Beam project, we've got a Jenkins job that stages the site:
https://github.com/apache/beam/blob/master/.test-infra/jenkins/job_beam_PreCommit_Website_Stage.groovy
You can see Jenkins making a comment about where the staged contents are,
as here: https://github.com/apache/beam-site/pull/273.
Beam pushed daily snapshots to nexus until the change where our (donated)
Jenkins executors were moved outside of Infra's purview. Beam migrated from
Maven to Gradle while maintaining the functionality. I don't know if
anything special had to be done. Added Yifan who I think knows the most
about th
radle/BeamModulePlugin.groovy#L573
Kenn
On Sun, Apr 21, 2019 at 4:45 PM Antoine Toulme wrote:
> I’ll take any idea. I looked at the beam builds, nothing in there seems to
> be uploading snapshots?
>
> It might be time to move to Maven to fit the mold.
>
> > On Apr 18, 2019, at 3:06
Feb 29, on a slave that is
> disconnected now.
>
>
> > On Apr 21, 2019, at 10:46 PM, Antoine Toulme
> wrote:
> >
> > Thank you both. I’m stealing that code.
> >
> >> On Apr 21, 2019, at 8:00 PM, Kenneth Knowles wrote:
> >>
> >> This
open to fix this?
>
> Alternatively, jenkins could store the credentials and inject them in the
> build.
>
> Where can I get more context?
>
> > On Apr 22, 2019, at 08:08, Kenneth Knowles wrote:
> >
> > Yes, this is because previously these boxes were manag
elpful for us).
On Mon, Apr 22, 2019 at 9:02 AM Kenneth Knowles wrote:
> It looks like your other thread has a part of the answer. There's no plan
> to get the credentials onto external VMs as it used to, but the publish
> command itself could run on ASF-managed instances.
>
>
Has this support already been removed?
All of Beam's jobs use this plugin. They are generated using the job DSL,
but we have not ported to the other plugin.
Kenn
On Wed, Jul 10, 2019 at 1:33 PM Daniel Gruno wrote:
> Hi folks,
> as part of some cleanup and consolidation (essentially we don't wa
(Top-posting a question that rewinds this thread a bit. Feel to continue
other discussion on the latest inline email)
Why do so many tools require write access? It seems like there's at least
*some* part of this that is a technical limitation... dare I say "error"?
My years-stale understanding (f
Beam was just discussing this. Was there any conclusion? Is there an ASF Infra
build cache? Or is there now a project that did it themselves we can learn from?
On 2019/12/29 12:15:59, Vladimir Sitnikov wrote:
> >Trying to get the use case
>
> Please check the first mail. It is there.
>
> For
12 matches
Mail list logo
