Revise GH workflow #23

Closed
opened 2025-12-28 18:11:13 +00:00 by sami · 3 comments
Owner

Originally created by @smallhive on GitHub (Sep 14, 2023).

We need to revise current repo workflows connected with docker images

Current Behavior

Each push make a new docker version and pushes it to DockerHub

Expected Behavior

Push new images only on release

Possible Solution

Update workflow

Originally created by @smallhive on GitHub (Sep 14, 2023). We need to revise current repo workflows connected with docker images ## Current Behavior Each push make a new docker version and pushes it to DockerHub ## Expected Behavior Push new images only on release ## Possible Solution Update workflow
sami 2025-12-28 18:11:13 +00:00
  • closed this issue
  • added the
    U4
    bug
    S2
    I4
    labels
Author
Owner

@roman-khimov commented on GitHub (Sep 14, 2023):

The problem is exactly that it's not a Github action. It's buried deeply in Jenkins pipelines.

@roman-khimov commented on GitHub (Sep 14, 2023): The problem is exactly that it's _not_ a Github action. It's buried deeply in Jenkins pipelines.
Author
Owner

@smallhive commented on GitHub (Sep 14, 2023):

Whoops, one will detect this when starting to work on the issue

@smallhive commented on GitHub (Sep 14, 2023): Whoops, one will detect this when starting to work on the issue
Author
Owner

@roman-khimov commented on GitHub (Sep 14, 2023):

In fact it's a nice issue to rework this flow into GH action.

@roman-khimov commented on GitHub (Sep 14, 2023): In fact it's a nice issue to rework this flow into GH action.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
nspcc-dev/neofs-aio#23
No description provided.