You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ctakes.apache.org by "Finan, Sean" <Se...@childrens.harvard.edu.INVALID> on 2024/07/29 15:14:51 UTC
Re: Build cTAKES using GitHub action? [EXTERNAL]
> Btw. how about setting up a GitHub action for building cTAKES?
I thought about that when we switched over from svn. I didn't do it myself because I am happy with Jenkins. It also seems like quite the beast to romp around in a GH action. I suppose that we could have build profiles that only compile the basic modules that are in the default clinical pipeline and things like that. Even without that, I don't think that we'd have problems with the infra rules https://infra.apache.org/github-actions-policy.html
I don't place that as a high priority, but if anybody else does then I say "go for it". https://infra.apache.org/github-actions-secrets.html
Sean
________________________________
From: Richard Eckart de Castilho <re...@apache.org>
Sent: Friday, July 26, 2024 8:45 PM
To: dev@ctakes.apache.org <de...@ctakes.apache.org>
Subject: Build cTAKES using GitHub action? [EXTERNAL]
* External Email - Caution *
Btw. how about setting up a GitHub action for building cTAKES?
-- Richard
Re: Build cTAKES using GitHub action? [EXTERNAL]
Posted by "Finan, Sean" <Se...@childrens.harvard.edu.INVALID>.
I am pretty sure that nobody would mind ... The great thing about version control is that what has been done can always be undone.
________________________________
From: Richard Eckart de Castilho <re...@apache.org>
Sent: Monday, July 29, 2024 3:38 PM
To: dev@ctakes.apache.org <de...@ctakes.apache.org>
Subject: Re: Build cTAKES using GitHub action? [EXTERNAL]
* External Email - Caution *
> On 29. Jul 2024, at 12:14, Finan, Sean <Se...@childrens.harvard.edu.INVALID> wrote:
>
>> Btw. how about setting up a GitHub action for building cTAKES?
>
> I thought about that when we switched over from svn. I didn't do it myself because I am happy with Jenkins.
Right, I honestly forgot that there's Jenkins.
I guess that's because I didn't see Jenkins badges on the PRs:
* https://urldefense.com/v3/__https://github.com/apache/ctakes/pull/21__;!!NZvER7FxgEiBAiR_!qsgb8wTFlVoBS9VU86JKrNyrbAQfAQd4MZIEkmpDyK3h10xw0SEz1iNheVt5Z6JaJB4XtWER6vxs-6jITDLAuw$
Cf.
* https://urldefense.com/v3/__https://github.com/apache/uima-uimaj/pull/370__;!!NZvER7FxgEiBAiR_!qsgb8wTFlVoBS9VU86JKrNyrbAQfAQd4MZIEkmpDyK3h10xw0SEz1iNheVt5Z6JaJB4XtWER6vxs-6id7fIEbg$
I can see you're still using "traditional" UI-configured Jenkins jobs instead of Jenkins pipelines
that are managed in the version control.
Would you mind if I set up a pipeline build that can handle PRs for cTAKES by copying the approach
I have taken in UIMA?
See also:
* https://urldefense.com/v3/__https://ci-builds.apache.org/job/UIMA/job/uima-uimaj/__;!!NZvER7FxgEiBAiR_!qsgb8wTFlVoBS9VU86JKrNyrbAQfAQd4MZIEkmpDyK3h10xw0SEz1iNheVt5Z6JaJB4XtWER6vxs-6i67BviWg$
* https://urldefense.com/v3/__https://ci-builds.apache.org/job/UIMA/configure__;!!NZvER7FxgEiBAiR_!qsgb8wTFlVoBS9VU86JKrNyrbAQfAQd4MZIEkmpDyK3h10xw0SEz1iNheVt5Z6JaJB4XtWER6vxs-6hzipOuGA$
* https://urldefense.com/v3/__https://ci-builds.apache.org/job/UIMA/job/uima-uimaj/configure__;!!NZvER7FxgEiBAiR_!qsgb8wTFlVoBS9VU86JKrNyrbAQfAQd4MZIEkmpDyK3h10xw0SEz1iNheVt5Z6JaJB4XtWER6vxs-6j88KBB1w$
That approach is using a shared repo that contains the actual pipeline configuration which is
used by all UIMA sub-projects. I'd probably temporarily use that for cTAKES as well but it should
eventually be cloned to a separate repo for cTAKES.
* https://urldefense.com/v3/__https://github.com/apache/uima-build-jenkins-shared-library/tree/main__;!!NZvER7FxgEiBAiR_!qsgb8wTFlVoBS9VU86JKrNyrbAQfAQd4MZIEkmpDyK3h10xw0SEz1iNheVt5Z6JaJB4XtWER6vxs-6iYqO2wXQ$
Cheers,
-- Richard
Re: Build cTAKES using GitHub action?
Posted by Richard Eckart de Castilho <re...@apache.org>.
> On 29. Jul 2024, at 12:14, Finan, Sean <Se...@childrens.harvard.edu.INVALID> wrote:
>
>> Btw. how about setting up a GitHub action for building cTAKES?
>
> I thought about that when we switched over from svn. I didn't do it myself because I am happy with Jenkins.
Right, I honestly forgot that there's Jenkins.
I guess that's because I didn't see Jenkins badges on the PRs:
* https://github.com/apache/ctakes/pull/21
Cf.
* https://github.com/apache/uima-uimaj/pull/370
I can see you're still using "traditional" UI-configured Jenkins jobs instead of Jenkins pipelines
that are managed in the version control.
Would you mind if I set up a pipeline build that can handle PRs for cTAKES by copying the approach
I have taken in UIMA?
See also:
* https://ci-builds.apache.org/job/UIMA/job/uima-uimaj/
* https://ci-builds.apache.org/job/UIMA/configure
* https://ci-builds.apache.org/job/UIMA/job/uima-uimaj/configure
That approach is using a shared repo that contains the actual pipeline configuration which is
used by all UIMA sub-projects. I'd probably temporarily use that for cTAKES as well but it should
eventually be cloned to a separate repo for cTAKES.
* https://github.com/apache/uima-build-jenkins-shared-library/tree/main
Cheers,
-- Richard