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

Refactor use_tic() #193

Merged
merged 18 commits into from
Nov 27, 2019
Merged

Refactor use_tic() #193

merged 18 commits into from
Nov 27, 2019

Conversation

pat-s
Copy link
Member

@pat-s pat-s commented Oct 24, 2019

Changes

  • Add new templates: Asks the user what to build (single/matrix, Linux/macOS), which CI provider to use at all and if multiple R versions are desired

  • Update templates

    • install pkgs in parallel
    • use ccache for faster re-installs of compiled code
  • move some functions to their own .R file to clean up a bit

  • update vignette

  • use the cli package (dev version) for more sophisticated cli output

  • removes the after_install stage as this stage is deprecated by Travis

  • adds some info to the tic.R template

  • update badges

    • add codecov badge
    • use shield.io badges
  • export use_*_yml() functions so that users can install yml templates without use_tic()

@pat-s pat-s requested a review from krlmlr October 31, 2019 20:47
@pat-s pat-s marked this pull request as ready for review October 31, 2019 20:47
@pat-s pat-s mentioned this pull request Oct 31, 2019
25 tasks
Copy link
Collaborator

@krlmlr krlmlr left a comment

Choose a reason for hiding this comment

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

Thanks. This is too large for a review. I can use it the next time I need to set up a project.

Maintaining multiple .yml templates for each CI platform seems like a nightmare in the long run. Is there any chance to generalize this?

@@ -11,7 +11,6 @@ before_install:
- R -q -e 'remotes::install_local(getwd(), force = TRUE); print(tic::dsl_load()); tic::prepare_all_stages()'
- R -q -e 'tic::before_install()'
install: R -q -e 'tic::install()'
after_install: R -q -e 'tic::after_install()'
Copy link
Collaborator

Choose a reason for hiding this comment

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

Is this intended?

Copy link
Member Author

Choose a reason for hiding this comment

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

This stage is not supported (anymore) by Travis. Discovered this by running the official Travis lintr.

Copy link
Member Author

Choose a reason for hiding this comment

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

Maintaining multiple .yml templates for each CI platform seems like a nightmare in the long run. Is there any chance to generalize this?

We could trim it down to one file for "build", "deploy" and "meta" (matrix, libs) and cat them together when building the template. This way, we would only have to maintain three files at max per CI provider.

Copy link
Collaborator

Choose a reason for hiding this comment

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

Sounds good.

@@ -11,7 +11,6 @@ before_install:
- R -q -e 'remotes::install_local(getwd(), force = TRUE); print(tic::dsl_load()); tic::prepare_all_stages()'
- R -q -e 'tic::before_install()'
install: R -q -e 'tic::install()'
after_install: R -q -e 'tic::after_install()'
Copy link
Collaborator

Choose a reason for hiding this comment

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

Sounds good.

@krlmlr krlmlr merged commit 8d76ddb into master Nov 27, 2019
@krlmlr krlmlr deleted the smart-use-tic branch November 27, 2019 11:06
@krlmlr
Copy link
Collaborator

krlmlr commented Nov 27, 2019

Thanks!

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.

2 participants