Giter VIP home page Giter VIP logo

docker-perl-tester's People

Contributors

atoomic avatar dependabot[bot] avatar happy-barney avatar manchicken avatar oalders avatar rafork avatar rjbs avatar rspier avatar szabgab avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar

docker-perl-tester's Issues

Adding other modules - what is your policy?

I just bumped into this image and started to use it.
The first thing I wanted to use it with also asked to install

JSON and Alien::Build

Another project required

Test::Requires, Plack::Test, Test::SharedFork, Test::TCP, Test::Time (and probably a few others)

I'd be glad to send the respective PRs, but I thought I'd ask first what do you think?
What is your policy of inclusion.

smoke PRs to detect issues earlier

This was discussed in #13 and @oalders suggested to create one action to smoke PRs
so we can detect issues when adding new modules for example.

At this day we only build on the main branches

Provide App::perlimports to the image

Hi,

I am fond of perlimports for cleaning up my import statements. Would it make sense to add that module to the image? The list of dependencies looks a bit daunting though.

Edit: The issue with DBD::ODBC was unrelated.

please provide a devel build

See Perl/docker-perl#125

docker-perl has very graciously added a monthly "devel" build of perl's latest dev snapshot, like the current v5.37.8

Being able to test against "latest blead" would be very useful!

I afraid I am unlikely to volunteer for this work, as I barely know how to operate Docker, so instead I hope someone else will be excited by this news and do whatever must be done. :)

Help request: dzil: not found

Hi. I've just started using docker-perl-tester (via github actions). I'm using perl-tester:5.14 to :5.36 and :latest, and Dist::Zilla is documented (in the README.md) as being available from :5.14 onwards, but all my dzil commands (e.g., dzil authordeps --missing | cpanm --notest) result in dzil: not found in the log. Any idea what I'm doing wrong? I checked that /usr/local/bin is in $PATH, and it is. Then I added find /usr -type f -name dzil to the github actions but it found nothing. The dzil command does come with Dist::Zilla, doesn't it? Or have I been spoiled by debian's libdist-zilla-perl package? How do I install dzil? Also, why isn't it there? I've seen a tutorial online that uses dzil without any obvious attempt to install it explicitly (https://perlmaven.com/setup-github-actions). What am I missing? I just added find / -type f -name Zilla.pm to the actions it didn't find Dist::Zilla. This is looking wierd. I even tried to cpanm --notest Dist::Zilla but that failed with:

! Configure failed for Dist-Zilla-6.030. See /github/home/.cpanm/work/1683541347.105/build.log for details.`
Configuring Dist-Zilla-6.030 ... N/A
##[error]Process completed with exit code 1.

Any advice would be appreciated. I've included my github actions yml file (without the above experiments) in case that helps.
ci.yml.txt

The errors above were for :5.14. I just checked your Dockerfile's cpanfile and it doesn't mention Dist::Zilla until version 5.20 (not 5.14 as stated in the README.md). Does that mean the README.md is wrong, and that Dist::Zilla is only available with :5.20 and above? If so, please fix the README.md (or make what it says true).

Also, I checked the logs for :latest, which does have Dist::Zilla, and it fails differently:

! Finding Test::FailWarnings~"0" on cpanmetadb failed.
! Finding Test::FailWarnings~"0" () on mirror http://www.cpan.org failed.
! Couldn't find module or a distribution Test::FailWarnings~"0"
! Finding Test::Kwalitee~"1.21" on cpanmetadb failed.
! Finding Test::Kwalitee~"1.21" () on mirror http://www.cpan.org failed.
! Couldn't find module or a distribution Test::Kwalitee~"1.21"

I don't know why these modules can't be found (or where the v1.21 comes from).

Maybe I should just abandon using dzil in github actions, and just run prove -l.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.