GithubHelp home page GithubHelp logo

wooga / atlas-release Goto Github PK

View Code? Open in Web Editor NEW
0.0 40.0 2.0 402 KB

gradle release plugin for atlas library packages

Home Page: https://wooga.github.io/atlas-release

License: Apache License 2.0

Groovy 94.63% HTML 1.92% Shell 0.34% Dockerfile 0.66% Mustache 2.45%
wooga gradle internal plugin release atlas

atlas-release's People

Watchers

 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  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Forkers

isabella232

atlas-release's Issues

Add Documentation for Release version number calculation

The logic and changes to Nebular Release are so big that it is not easy to understand when and how we calculate the version for the project to be build. Create a Wiki page with examples and explanation how the version number gets calculated by the base plugins and the custom wooga strategies.

Dependabot couldn't authenticate with https://wooga.jfrog.io/wooga/atlas-maven

Dependabot couldn't authenticate with https://wooga.jfrog.io/wooga/atlas-maven.

Dependabot tried to authenticate with your details, but authentication failed. This could be because the details are no longer valid or because they don't grant permission to access all of the dependencies required.

Please note that for JFrog repositories Dependabot needs to have deploy permission (as JFrog requires this for Dependabot to access uncached artifacts).

You can provide authentication details in your Dependabot dashboard by clicking into the account menu (in the top right) and selecting 'Config variables'.

View the update logs.

Set also dependency to sub setup task if unity plugin is applied

private configureUnityPackageIfPresent(Project project) {
DependencyHandler dependencies = project.dependencies
project.subprojects { sub ->
sub.afterEvaluate {
logger.info("check subproject {} for unity plugin", sub.name)
if (sub.plugins.hasPlugin("net.wooga.unity")) {
logger.info("subproject {} has unity plugin.", sub.name)
logger.info("configure dependencies {}", sub.path)
dependencies.add(ARCHIVES_CONFIGURATION, dependencies.project(path: sub.path, configuration: "unitypackage"))
logger.info("create cleanMetaFiles task")
Delete cleanTask = (Delete) sub.tasks.create(name: CLEAN_META_FILES_TASK, type: Delete)
def files = project.fileTree(new File(sub.projectDir, 'Assets/'))
files.include(extension.metaCleanPattern.includes)
files.exclude(extension.metaCleanPattern.excludes)
cleanTask.delete(files)
project.tasks.withType(PaketPack, new Action<PaketPack>() {
@Override
void execute(PaketPack paketPack) {
paketPack.dependsOn cleanTask
}
})
}
}
}
}

Add dependency here

Dependabot couldn't authenticate with https://wooga.jfrog.io/wooga/atlas-maven

Dependabot couldn't authenticate with https://wooga.jfrog.io/wooga/atlas-maven.

Dependabot tried to authenticate with your details, but authentication failed. This could be because the details are no longer valid or because they don't grant permission to access all of the dependencies required.

Please note that for JFrog repositories Dependabot needs to have deploy permission (as JFrog requires this for Dependabot to access uncached artifacts).

You can provide authentication details in your Dependabot dashboard by clicking into the account menu (in the top right) and selecting 'Config variables'.

View the update logs.

Final release produces a Prerelease on when publish Github Release

Description

When executing a final release for a WDK project the actual github release is marked as prerelease.
I checked the code and it looks like we changed the check values during the gradle upgrade process.
Currently we check for project.status != 'final'.
as seen here:

githubPublishTask.prerelease.set(project.provider { project.status != 'final' })

The old code did check
githubPublishTask.setPrerelease({ project.status != 'release' })

We need to fix this and maybe provide a test case to verify this.

Setup should call paket restore instead of install

We should make sure that the setup step is deterministic for CI environments.

from paket install doc page:

Unlike paket update, paket install will only look for new versions of dependencies that have been modified in paket.dependencies and use the version from paket.lock for all other dependencies.

from paket restore doc page:

paket restore fails with an error if the paket.lock file does not exist. No packages are downloaded in that case. Please see paket install and paket update to learn how to create the paket.lock file.

So the setup task should depend on paket restore if a paket.lock file can be found, and paket install if not.

private static Task configureSetupTask(final Project project) {
project.tasks.maybeCreate(SETUP_TASK).with {
dependsOn(PaketGetPlugin.INSTALL_TASK_NAME)
group = GROUP
setDescription("run project setup")
}
}

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.