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

feat: support workspaces for go #864

Merged
merged 22 commits into from
Oct 18, 2024
Merged

feat: support workspaces for go #864

merged 22 commits into from
Oct 18, 2024

Conversation

sergiusens
Copy link
Collaborator

  • Have you signed the CLA?

Copy link

@bowenfan96 bowenfan96 left a comment

Choose a reason for hiding this comment

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

Thanks very much Sergio! This is just as we discussed and looks great to me with my limited knowledge on craft plugins. I raised a minor point about not supporting existing go.work files inline.

craft_parts/plugins/go_plugin.py Outdated Show resolved Hide resolved
docs/common/craft-parts/reference/plugins/go_plugin.rst Outdated Show resolved Hide resolved
docs/common/craft-parts/reference/plugins/go_plugin.rst Outdated Show resolved Hide resolved
tests/integration/plugins/test_go.py Outdated Show resolved Hide resolved
Signed-off-by: Sergio Schvezov <[email protected]>
We cannot guarantee consistent results, the build should fail at this
point until we have a mechanism to validate steps.

Signed-off-by: Sergio Schvezov <[email protected]>
Signed-off-by: Sergio Schvezov <[email protected]>
Signed-off-by: Sergio Schvezov <[email protected]>
@sergiusens
Copy link
Collaborator Author

There is a how do we clean item to deal with, but might need to come later

Signed-off-by: Sergio Schvezov <[email protected]>
@tigarmo
Copy link
Contributor

tigarmo commented Oct 17, 2024

image
😿 😭

Signed-off-by: Sergio Schvezov <[email protected]>
@sergiusens
Copy link
Collaborator Author

@tigarmo sorry about that, there is nothing really left from the original implementation

Copy link
Contributor

@tigarmo tigarmo left a comment

Choose a reason for hiding this comment

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

@sergiusens can you talk about the motivation for moving on from the previous implementation to this one?

craft_parts/plugins/go_use_plugin.py Outdated Show resolved Hide resolved
craft_parts/plugins/go_use_plugin.py Show resolved Hide resolved
craft_parts/plugins/go_plugin.py Outdated Show resolved Hide resolved
Signed-off-by: Sergio Schvezov <[email protected]>
Copy link
Collaborator

@cmatsuoka cmatsuoka left a comment

Choose a reason for hiding this comment

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

This seems to do what was discussed. Ordinarily I would call this an experimental plugin but in the use context it would be rather inconvenient to have to plaster --use-experimental-plugins everywhere. It should be fine if we properly address global state handling early next cycle.

craft_parts/plugins/go_use_plugin.py Show resolved Hide resolved
craft_parts/plugins/go_use_plugin.py Outdated Show resolved Hide resolved
sergiusens and others added 2 commits October 18, 2024 14:45
Signed-off-by: Sergio Schvezov <[email protected]>
@sergiusens sergiusens merged commit 57cf26f into main Oct 18, 2024
13 checks passed
@sergiusens sergiusens deleted the feature/go-workspaces branch October 18, 2024 21:36
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.

4 participants