concourse/pool-resource issues and pull requests

#67 - fix the mess I made in PR #66

Pull Request - State: closed - Opened by taylorsilva over 1 year ago

#66 - Add check operation

Pull Request - State: closed - Opened by adnankobir over 1 year ago - 2 comments

#65 - Avoid hard code git user name/email is already set

Pull Request - State: closed - Opened by ywei2017 over 2 years ago - 4 comments

#64 - git_lock_handler hardcodes git config info

Issue - State: closed - Opened by ywei2017 almost 3 years ago - 1 comment

#63 - Lack of support for "git_config"

Issue - State: closed - Opened by ywei2017 about 3 years ago - 1 comment

#62 - Add HTTP Proxy support for SSH

Pull Request - State: closed - Opened by Aggouri over 3 years ago - 1 comment

#61 - switch to Go modules

Pull Request - State: closed - Opened by vito over 3 years ago
Labels: release/no-impact

#60 - fix `private_key` usage on alpine image

Pull Request - State: closed - Opened by aoldershaw almost 4 years ago
Labels: bug

#59 - concourse/pool-resource:1.1.5 (-alpine) is missing ssh-agent

Issue - State: closed - Opened by dsharp-pivotal almost 4 years ago - 3 comments

#58 - use alpine:latest and ubuntu:latest as base

Pull Request - State: closed - Opened by vito almost 4 years ago
Labels: release/no-impact, misc

#57 - Failed to authenticate with private_key

Issue - State: closed - Opened by schmurfy about 4 years ago - 1 comment

#56 - Revert "Make depth of 1 to be the default"

Pull Request - State: closed - Opened by vito over 4 years ago - 2 comments

#55 - getting ressource fails with: fatal: ambiguous argument 'HEAD~1'

Issue - State: closed - Opened by c0d1ngm0nk3y over 4 years ago - 2 comments

#54 - basename: missing operand

Issue - State: closed - Opened by elgohr over 4 years ago - 2 comments

#53 - Remove link to concourse.ci

Issue - State: closed - Opened by releen almost 5 years ago - 1 comment

#52 - Make depth of 1 to be the default

Pull Request - State: closed - Opened by sc68cal almost 5 years ago - 6 comments

#51 - Add an example for using the claim and release

Pull Request - State: closed - Opened by sc68cal about 5 years ago - 1 comment

#50 - Adds optional depth parameter for specifying the number of git commits

Pull Request - State: closed - Opened by maryamklabib over 5 years ago - 2 comments
Labels: release/documented

#49 - Clones only the history leading to the tip of a single branch.

Pull Request - State: closed - Opened by maryamklabib over 5 years ago - 1 comment
Labels: release/documented

#48 - add diff_filter param to source config [closing #47]

Pull Request - State: closed - Opened by fredwangwang over 5 years ago - 4 comments

#47 - feature request: custom rules for checking

Issue - State: closed - Opened by fredwangwang over 5 years ago

#46 - missing ability to customize git user and email

Issue - State: closed - Opened by bencao over 5 years ago - 2 comments

#45 - Migrating to ubuntu base image

Pull Request - State: closed - Opened by YoussB over 5 years ago

#44 - Add the team name to the commit log

Pull Request - State: closed - Opened by odormond almost 6 years ago - 4 comments
Labels: enhancement

#43 - Read lock name from file

Issue - State: open - Opened by dvianello about 6 years ago - 2 comments

#42 - Always print when we are starting

Pull Request - State: closed - Opened by marco-m about 6 years ago - 5 comments
Labels: enhancement

#41 - Make evident how much time the resource is waiting to acquire a lock

Issue - State: closed - Opened by marco-m about 6 years ago - 2 comments

#40 - Use shallow git clones

Issue - State: open - Opened by vlad-stoian about 6 years ago

#39 - Support Freeing Locks held beyond some threshhold

Issue - State: open - Opened by vcase over 6 years ago - 4 comments

#38 - Releasing lock ignores metadata

Issue - State: open - Opened by rjosephwright over 6 years ago

#37 - Implement an atomic lock check action.

Pull Request - State: closed - Opened by josecv over 6 years ago - 8 comments
Labels: needs-validation

#36 - Ability to specify maximum number of retries?

Issue - State: closed - Opened by aegershman over 6 years ago

#35 - Adds support for weighted lock

Issue - State: open - Opened by loganmzz over 6 years ago

#34 - Add atomic update operation

Pull Request - State: closed - Opened by EleanorRigby almost 7 years ago - 7 comments
Labels: enhancement

#33 - Triggering suppression

Pull Request - State: closed - Opened by glyn almost 7 years ago - 5 comments
Labels: needs-validation

#32 - `get` on a pool resource should fail if named lock is unclaimed

Issue - State: open - Opened by staylor14 almost 7 years ago

#31 - Get behaviour does not match README

Issue - State: open - Opened by theozaurus almost 7 years ago - 1 comment
Labels: question

#30 - pool-resource needs an atomic move operation

Issue - State: open - Opened by chendrix over 7 years ago - 1 comment

#29 - `get` on a pool-resource should work when there is only one commit

Issue - State: open - Opened by geofffranks over 7 years ago - 4 comments
Labels: bug

#28 - WIP - Actually vendor dependencies

Pull Request - State: closed - Opened by zachgersh over 7 years ago - 11 comments

#27 - Adding a lock should reliably fail when the pool contains a lock by that name

Issue - State: open - Opened by jaresty over 7 years ago - 3 comments
Labels: bug

#26 - Claims environment but task never finishes

Issue - State: open - Opened by ameowlia over 7 years ago - 4 comments
Labels: bug

#25 - Getting two environments at a time

Issue - State: open - Opened by ameowlia over 7 years ago - 1 comment
Labels: bug

#24 - skip_ssl_verification option for git repos

Issue - State: closed - Opened by mehrotra-prateek over 7 years ago - 2 comments

#23 - Correct examples so they release locks on failure

Pull Request - State: closed - Opened by jfuerth over 7 years ago - 5 comments

#22 - Releasing lock in on_failure step does not work

Issue - State: closed - Opened by mariash about 8 years ago - 3 comments

#21 - Having trouble stabilizing a demonstration pipeline

Issue - State: closed - Opened by hfinucane about 8 years ago - 7 comments
Labels: question

#20 - Error releasing pool resource if build is cancelled before it acquires lock

Issue - State: closed - Opened by xtremerui over 8 years ago - 4 comments

#19 - Revert tolerance of in-place file modifications

Pull Request - State: closed - Opened by rainmaker over 8 years ago - 2 comments

#18 - Remove # from buildId/buildName so github doesn't link them to existing

Pull Request - State: closed - Opened by geramirez over 8 years ago - 5 comments

#17 - "Escaping" buildId and buildName so github doesn't link them to existing …

Pull Request - State: closed - Opened by geramirez over 8 years ago - 2 comments

#16 - No helpful error output when private key provided requires password

Issue - State: open - Opened by ghost over 8 years ago - 2 comments

#15 - username and password auth for HTTP(S) added

Pull Request - State: closed - Opened by JamesClonk over 8 years ago - 1 comment

#14 - Commit message for put step should include act_external_url

Issue - State: open - Opened by danger-ranger over 8 years ago - 1 comment

#13 - Change update help if ginkgo is not installed

Pull Request - State: closed - Opened by kindrowboat over 8 years ago - 2 comments

#12 - Inconsistent naming scheme

Issue - State: closed - Opened by supertopher over 8 years ago - 2 comments

#11 - File modifications in-place don't break locks

Pull Request - State: closed - Opened by rainmaker over 8 years ago - 4 comments

#10 - Do locks leak?

Issue - State: closed - Opened by tomwhoiscontrary over 8 years ago - 6 comments

#9 - Update README to include units on retry_delay

Pull Request - State: closed - Opened by jenspinney almost 9 years ago - 4 comments

#8 - Update README with info about add_claimed

Pull Request - State: closed - Opened by moredip almost 9 years ago - 2 comments

#7 - add an `add_claimed` operation to `out` command

Pull Request - State: closed - Opened by moredip almost 9 years ago

#6 - Unable to lock/release more than once from the same pool within a task

Issue - State: closed - Opened by jdeppe-pivotal about 9 years ago - 11 comments

#5 - Getting a lock from a previous job fails sometimes

Issue - State: closed - Opened by mhoran about 9 years ago - 2 comments

#4 - Git commit messages should contain build information

Issue - State: closed - Opened by chendrix about 9 years ago - 2 comments

#3 - Claiming lock on .gitkeep file

Issue - State: closed - Opened by shashwathi about 9 years ago - 3 comments

#2 - Claiming too quickly after an unclaim causes 'error: lock instance is no longer acquired'

Issue - State: closed - Opened by topherbullock about 9 years ago - 5 comments
Labels: bug

#1 - Highlights the importance of `private_key` in `source`

Pull Request - State: closed - Opened by cunnie over 9 years ago - 1 comment

GitHub / concourse/pool-resource issues and pull requests