Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[???] Add build action for PRs #370

Open
wants to merge 13 commits into
base: main
Choose a base branch
from

Conversation

MartinFlores751
Copy link
Contributor

Ccache can be removed if we want a clean build every run.

@korydraughn
Copy link
Contributor

After thinking about this a little more, making sure the project compiles correctly is more important than the amount of time taken to build it.

Let's remove/disable ccache for now.

@MartinFlores751
Copy link
Contributor Author

Do we also want this to run on main, or just PRs?

@korydraughn
Copy link
Contributor

On PRs is good. See irods/irods for reference.

@MartinFlores751
Copy link
Contributor Author

I'll take out cache and put in a separate draft so we won't forget about it

@MartinFlores751
Copy link
Contributor Author

On PRs is good. See irods/irods for reference.

In that case, only thing to do is remove cache. Already only acts on PRs.

@MartinFlores751 MartinFlores751 marked this pull request as ready for review November 15, 2024 18:55
Copy link
Contributor

@korydraughn korydraughn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good. Nice and clean.

steps:
- name: Checkout Repository
uses: actions/checkout@v4
- name: Install Misc
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's use the same wording as in irods/irods for this.

  • Install Prerequisites

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Avoided that name initially since I wasn't sure what exactly are the prerequisites.

@@ -0,0 +1,54 @@
name: iRODS HTTP API Builder
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looking at irods/irods, how do you feel about changing this to one of the following?

  • Build-Ubuntu
  • build-irods-http-api-ubuntu

Then we could expand this to cover other versions of Ubuntu, and later other platforms such as EL8 and EL9.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it would be better without the hyphens. This name is supposed to be a user-facing name. You can see this in the passed checks at the bottom.

Perhaps we can name it so it ends up as Ubuntu iRODS HTTP API Builder / Build iRODS HTTP API - <Specific Ubuntu Image Here>?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sure. I don't think hyphens make it less readable.

Try expanding the builder workflow to support ub22/24, EL8/9 and see how the github actions report it. We want things to be sorted, grouped, and organized.

Aim for consistency across repos.

Take a look at the workflows for irods/irods.

Comment on lines +31 to +32
irods-dev=4.3.2-0~jammy \
irods-runtime=4.3.2-0~jammy

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are we using 4.3.2 here because it's the declared minimum required version in the CMakeLists?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

4.3.2 since the builder docker file uses 4.3.2.

If we want, we could matrix this I think?

@alanking
Copy link

Also, needs an issue number. Seems good overall

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants