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

Conda build should have several stages to be called independently #4471

Closed
oleg-alexandrov opened this issue May 16, 2022 · 4 comments
Closed
Labels
backlog issue has been triaged but has not been earmarked for any upcoming release locked [bot] locked due to inactivity source::community catch-all for issues filed by community members stale::closed [bot] closed after being marked as stale stale [bot] marked as stale due to inactivity type::feature request for a new feature or capability

Comments

@oleg-alexandrov
Copy link
Contributor

Summary

The conda-build toolset is nice and save work, but can be a pain to use because it is very slow. Then, if it fails, one has to restart everything, wait for a long time, and then likely fail again, and having to restart.

It should have the ability to resume a failed build, and also to resume at packaging, if that step failed. This would really save a lot of work.

Linked Issues & PRs

None

@oleg-alexandrov oleg-alexandrov added the epic a highlevel collection of smaller related issues label May 16, 2022
@LtDan33 LtDan33 closed this as completed Jun 3, 2022
@LtDan33 LtDan33 moved this to Done in 🧭 Planning Jun 3, 2022
@LtDan33 LtDan33 added off-topic not related to project, discussion is spam, or is otherwise nonsensical and removed epic a highlevel collection of smaller related issues labels Jun 3, 2022
@LtDan33 LtDan33 reopened this Jun 3, 2022
@LtDan33 LtDan33 added type::feature request for a new feature or capability backlog issue has been triaged but has not been earmarked for any upcoming release source::community catch-all for issues filed by community members and removed off-topic not related to project, discussion is spam, or is otherwise nonsensical labels Jun 3, 2022
@LtDan33
Copy link
Member

LtDan33 commented Jun 3, 2022

The epic label and issue is used to group tickets together by the conda-core devs, so removing for now.

@oleg-alexandrov
Copy link
Contributor Author

To add, it would be nice if this tool would have stages, such as:

conda-build --resume-build (resume latest build where it used to fail before, do not get dependencies)

conda-build --package (start at packaging, so after build/install)

This way the programmer can try to fix things then let conda-build take over.

@github-actions
Copy link

github-actions bot commented Jul 2, 2023

Hi there, thank you for your contribution!

This issue has been automatically marked as stale because it has not had recent activity. It will be closed automatically if no further activity occurs.

If you would like this issue to remain open please:

  1. Verify that you can still reproduce the issue at hand
  2. Comment that the issue is still reproducible and include:
    - What OS and version you reproduced the issue on
    - What steps you followed to reproduce the issue

NOTE: If this issue was closed prematurely, please leave a comment.

Thanks!

@github-actions github-actions bot added the stale [bot] marked as stale due to inactivity label Jul 2, 2023
@github-actions github-actions bot added the stale::closed [bot] closed after being marked as stale label Aug 29, 2023
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Aug 29, 2023
@oleg-alexandrov
Copy link
Contributor Author

Hoping this is looked into. Conda is so awfully slow, and debug cycles take a very long time. Conda should have a way of using a given environment without having to solve dependencies each time, and it should be able to resume where it failed.

@github-actions github-actions bot added the locked [bot] locked due to inactivity label Aug 20, 2024
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 20, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
backlog issue has been triaged but has not been earmarked for any upcoming release locked [bot] locked due to inactivity source::community catch-all for issues filed by community members stale::closed [bot] closed after being marked as stale stale [bot] marked as stale due to inactivity type::feature request for a new feature or capability
Projects
Archived in project
Development

No branches or pull requests

2 participants